Visual Basic vs Pony
When comparing Visual Basic vs Pony, the Slant community recommends Pony for most people. In the question“What are the best (productivity-enhancing, well-designed, and concise, rather than just popular or time-tested) programming languages?” Pony is ranked 22nd while Visual Basic is ranked 74th. The most important reason people chose Pony is:
The unique type system allows the compiler to automatically schedule actors on threads, giving you reliable concurrency for free.
Ranked in these QuestionsQuestion Ranking
Pros
Pro Very simple and efficient language (in terms of number of lines of code)
Pro Easy to learn
Pro Capable language
Compiling to the same intermediate language as C# and compiling against the same .NET libraries, the differences between C# and VB are largely syntactic. Most VB features even have a 1:1 correspondence with C#.
Pro Huge community
Being Microsoft's introductory language, visual basic has a strong and large community.
Pro English-like syntax
Pro Flexible, won't get in the way of a beginner
A beginner developer can worry about the code logic first, and then learn the language. Visual Basic lets you do basically anything if you really want, while still having the power to be a fully statically-typed and object oriented.
Pro Sibling to C#
If you don't want to start with C# because of its high learning floor, you can start with VB. It is dead easy to switch between the two.
Pro Easy to deal with Win32API
Using platform invoke, it's very easy to use the win32 api in vb.net. Neat and clean syntax. Not a mess like c# (meaning those "{}"s).
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 Almost as bad as Python, but less used
Con Bad reputation
Being a visual basic programmer, you're unlikely to be taken seriously by other programmers. According to the 2015 Stack Overflow survey, it was voted the second most dreaded language among developers.
Con Tends to get clunky due to prebuilt assets
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.