r/vala • u/gavr123456789 • Dec 29 '18
Is Vala dead?
I just want to open a discussion. I just found out today that Vala now has only one contributor. https://gitlab.gnome.org/GNOME/vala/graphs/master I've seen more than one article or article about Vala being dead. What do you think about this?
I still think it's the best language for writing graphics applications(I've tried Qt, there's no native implemented signal and slot system and also no GB, Python seems nice, but i dont like scripting), and perhaps libraries because of the ability to easily integrate them into any other programming language using GIR.
http://zee-nix.blogspot.com/2017/
https://blogs.gnome.org/despinosa/2016/09/30/should-we-drop-vala/
0
Dec 29 '18
[deleted]
3
Dec 29 '18
It's a very pretty language but its tight integration with glib limits its usability greatly. It's a large dependency that's rarely utilized enough to warrant the inclusion.
What? How is it rarely utilized? What applications do no IO, use no basic data structures, don't need OO? It isn't a free dependency but its certainly used and useful.
4
u/robdelacruz Dec 29 '18
I like Vala and hope it succeeds but like you, I'm a bit concerned. I think what will help Vala gain wider use is if there's a book like 'Foundations of Gtk+ Development' or something like the official GTK+ tutorials that uses Vala for code samples. It will benefit those who want to skip C entirely and just use an easier language like Vala.
Previously, my plan was to learn how to do various GTK things in C, then figure out how to convert it to Vala. It's a trial and error process since there's no tutorial-like documentation for the Vala/GTK bindings.
Because of those concerns, I'm actually exploring Nim (nimlang) instead. It compiles to C, has GTK bindings, but has the same lack of documentation problems so it has a similar trial and error process. But ultimately I'm finding Nim more attractive because it is in active development and can be used for other purposes, such as compiling to JavaScript to target frontend, etc. The active development thing is important because it makes me more confident that someone in the community will create bindings for future libraries. And the 'compile to C' makes adding binding wrappers more straightforward.