Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariRed/System vs Pony
When comparing Red/System vs Pony, the Slant community recommends Red/System for most people. In the question“What are the best systems programming languages?” Red/System is ranked 15th while Pony is ranked 20th. The most important reason people chose Red/System is:
Red has built-in support for concurrency and multi-core CPUs.
Question Ranking
Pros
Pro Built-in support for concurrency
Red has built-in support for concurrency and multi-core CPUs.
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 Doesn't work on 64-bit OSes
Still hasn't upgraded to be 64-bit OS compatible.
Con Not ready for production
Red is still on version 0.6.0. Which means that it still has some way to go before being used in production and in large projects.
Con All exceptions must be caught
The compiler enforces this, so code is littered with trys.
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 trys 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.
