When comparing Pony vs V, the Slant community recommends V for most people. In the question“What are the best systems programming languages?” V is ranked 5th while Pony is ranked 20th. The most important reason people chose V is:
V is easier than C and fast like C.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
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.
Pro Fast like C
V is easier than C and fast like C.
Pro C Interop
Can import C libraries, structs, and headers.
Pro Cross-platform
Compile to many OSes.
Pro Simplicity
V is simple and powerful.
Pro Can create multi-OS GUIs
Multi-OS GUI creation is more integrated into the language than others.
Pro Clear syntax
Highly understandable language.
Pro Sum types
V has Sum Types.
Pro Generics
V has generics.
Pro Closures
V has closures, which gives the user additional options and usefulness.
Pro Safety
V is very safe.
Pro Single paradigm
Follows the philosophy that there should be only one way to do something, as opposed to multi-paradigm languages like C++.
Pro Supports concurrency and channels
Can run functions concurrently that communicate over channels.
Pro Fast compile times
Compiles programs fast, less waiting around, so more productive and fun.
Pro Friendly and helpful community
Just check the V Discord channel or their GitHub Discussions and you will see by yourself.
Pro Inline assembly
Can add Assembly code.
Cons
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.
Con Rapid changes in a language syntax/features
Since V language under a continuous development and core syntax and features will be "frozen" in a version 1.0.0, updating from older version of a language can cause a code rewrite of previously working program.
Con V 1.0 release was planned for December 2019
The first version of the language was publicly released in June of 2019, version 0.1.x. First beta version of the language was released June of 2022, version 0.3. x. Language has progressed faster than most. Welcomes contributors to join the project.
