Re: [Vala] State of the Vala union

[Ulink <ulink gmx at>]

> > they have been part of a 200K lines of code project. They must have thought it was
> > production ready.

We are SURE that it was and it IS production ready. We started the
project approx. 2-3 years ago (vala 0.22 on Ubuntu 14.04 I think) and it
is constantly growing while implementing new features daily.

Choosing Vala+GLib+Gtk was a big luck. Curiously, against the
mainstream, we choosed it as a replacement for Qt! We implemented a 40k
LOC project using Qt before and were NOT satisfied, so we changed to
Vala+GLib+Gtk. Fortunately.

And we are compiling the app on Windows too using MSYS/mingw. At the
beginning, we only compiled the Vala created C sources on Windows (cool
feature, isn't it?). Mheanwile, we are compiling directly from the Vala
sources using valac on Windows.

There ARE some rough edges on Gtk/Windows, but Vala works very good even
on Windows. And there are some rough edges on Windows LOL, e.g. UDP
really sucks on Windows. But that's another story.

> Well, I suppose I have higher requirements than they have. From a production-ready
> compiler I would expect
> – no (or at best very obscure) type errors to get through
> – no compiler crashes
> – no broken code generated
> I don't think these are unreasonable criteria, yet valac fails all of them.

Until now, we NEVER had only one of these problems. Weird.

Honestly, we don't use 100.0% of all language features.

Thats because we are creating a real and usable application we can sell
to our customers and don't fiddle around with esoteric language features
only for the purpose to be the one and only real Vala master ;-)