When comparing Vala vs Pony, the Slant community recommends Vala for most people. In the question“What are the best systems programming languages?” Vala is ranked 17th while Pony is ranked 20th. The most important reason people chose Vala is:
Vala developed by Gnome Foundation.
Ranked in these QuestionsQuestion Ranking
Pros
Pro Rich GTK Support
Vala developed by Gnome Foundation.
Pro Fast
Underneath there is C. It makes some stuff easier to write than it would be with plain C code.
Pro Easy Syntax
Vala is syntactically similar to C# and includes several features such as: anonymous functions, signals, properties, generics, assisted memory management, exception handling, type inference, and foreach statements
Pro C compatible API (and ABI)
C programs can use libraries written in Vala, and vice versa.
Pro Good documentation
There is Valadoc and most of the libraries have Devhelp packages.
Pro Well-integrated with C language
Vala itself is compiled to C, therefore it can use the vast ecosystem of C language, with least effort.
Pro Stable ABI
You can write a library with ABI stability.
Pro A general purpose language
Vala is compiled to C and only requires GLib - or even nothing (posix profile)
Pro Concurrency model based on actors
The unique type system allows the compiler to automatically schedule actors on threads, giving you reliable concurrency for free.
Pro Reliable
Because of its capabilities secure type system, provided you don't use the C FFI, references will never be stale, race conditions are effectively impossible, deadlocks don't happen because locks and mutexes are never needed, and processes never crash because all exceptions must be handled. (Barring compiler bugs or external memory corruption, of course.) Pony programs can still lock up due to infinite loops, like any Turing-complete language.
Pro High performance
Compiles to native code, and features an intelligent garbage collector that takes advantage of the actor architecture to get essentially free garbage collection.
Pro Trivially simple C FFI
Calling low-level C functions is as simple as use "lib:clibrary"
and @c_function_name[return_type](parameter:type)
. Linking C to Pony libraries is just as easy, as the Pony compiler will generate appropriate header files.
Cons
Con Very few resources allocated to the language
Only a single person is working on Vala full time. Gnome Foundation isn't allocating sufficient resources to properly maintain Vala.
Con A very naïve approach to the real problem
Vala just adds more complexity to the game. No real benefits in using a 'programming language emulator' for UI code, you may think it adds to productivity but it's just a way to make the problem last longer, reinventing the wheel everytime and worse.
Con Very limited adoption
Vala isn't used in areas other than GTK development, and no major business has adopted the language.
Con Not a general purpose language
Can't use Vala in multiple software development areas.
Con Very limited tooling
Though using Gnome Builder, you can debug it easily.
Con Heavy reliance on GObject
Heavy reliance on GObject types, although Vala can be used without GObject. (posix profile)
Con Not well documented
It already has tons of documentation, even a book about Vala.https://leanpub.com/vala https://wiki.gnome.org/Projects/Vala/Documentation
Con No stable version
No stable version of Vala released for over a decade so far. Means that Vala isn't production ready.
Con All exceptions must be caught
The compiler enforces this, so code is littered with try
s.
Con Limited documentation
As Pony is such a new language, documentation is relatively light, and tutorials are few and far-between.
Con Few libraries
Con Garbage collector can't run until you yield
A long-running behavior can leak memory because the garbage collector has no chance to run.
Con Limited tooling
There's no IDE. Debuggers are fairly basic. Pony is too young to have much of an ecosystem.
Con Divide by zero is allowed
And instead of some sensible result like NaN or Inf, the answer is zero! Most languages would just raise an exception (and Pony used to do this), but since the compiler enforces the rule that "all exceptions must be caught" the proliferation of try
s was determined to be too burdensome on the programmer. This makes the whole design of the exception system questionable.
Con Unstable API
Pony is not ready for production. It has yet to release version 1.0, and there are frequent breaking changes.
Con Difficult learning curve
The type system uses a capabilities-oriented approach to reference semantics, which can be difficult to wrap your head around at first. The lack of more common object-oriented features and the preference for simplicity over familiarity can make it difficult for new users to model their program design.
