When comparing Vala vs Pharo, the Slant community recommends Vala for most people. In the question“What are the best languages to write a desktop Linux application in?” Vala is ranked 4th while Pharo is ranked 10th. The most important reason people chose Vala is:
Vala developed by Gnome Foundation.
Specs
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 Object-Oriented
In Pharo everything is an object. Compiler - object, network - object, method - also an object. And objects communicate with messages. No operators, no control-flow statements. Just objects and messages. Few things to learn, but you can learn OOP well.
Pro Easily learnt
There is good, free documentation including several books written by experts with extensive examples. There is an online MOOC. There are many tutorial videos. Supportive conferences and community. Even a professional support option if desired.
Pro Live updates
The nature of Pharo being a "live" environment allows you to perform live updates to your system without requiring to restart it. You can upgrade/modify classes while serving requests at the same time.
Pro Highly productive
Pro Seaside
The framework for developing sophisticated web applications in Smalltalk is developed in Pharo. Seaside lets you build highly interactive web applications quickly, reusably and maintainably.
Pro Remote debugging
Pro Beautiful coding patterns in your IDE
No need to search google for compact beautiful examples of how to do things, your live environment source is available and you can easily live search, see how it works and copy how the masters would do it (examples most languages still copy too).
Pro Glamorous toolkit & GTInspector
Most languages are still copying the Smalltalk tools of yesterday - GTInspector (written in Glamorous) takes live exploration of code/running objects to a new level. It's really slick, and better yet, you can easily write your own inspectors in 10 lines of code.
Pro Code can be run on rock solid GemStone environment
Pro 64 bit support as of Pharo 7
Use 32 bit or 64 bit versions of Pharo on Windows, Mac & Linux.
Pro Advanced code analysis tools
MOOSE environment provides extensive, easily leveraged and class leading tools for code analysis and improvement.
Pro Can run headless for production
Pro Really simple networking and REST with Zinc
Pro Graphics, graphing and visualisation framework - Roassal
Roassal and Mondrian provide fantastic and easily used frameworks for graphics, graphing and advanced visualisations (comparable to D3.js) but with much less code. Visualisations can be rendered into web friendly graphics (SVG, .png etc.) without additional work.
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 Small community
But they are very friendly and supportive. Best help comes through the mailing lists so not always easily googlable. There is also a Slack community where help is nearly instantaneous.
Con Odd language
Requires a different mindset. Much harder to apply what you know from popular or conventional languages . Switching over from or between other languages is more difficult.
Con Single threaded
Pharo's VM only ever uses one CPU core. If you want to write code that uses more than one CPU core, you need to jump through hoops such as running multiple VMs and synchronising your data.
