When comparing Nim vs Pony, the Slant community recommends Nim 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?” Nim is ranked 4th while Pony is ranked 28th. The most important reason people chose Nim is:
Checks your code at compile time.
Ranked in these QuestionsQuestion Ranking
Pro Strict typing
Checks your code at compile time.
Pro Really crossplatform
The same code can be used for web, server, desktop and mobile.
Pro Easy to read
Nim has a lot of common with Python in terms of syntax.
Indentation-based syntax, for/while loops
Pro Built-in Unicode support
You can use unicode names for variables, there is "unicode" module for operations with unicode
Pro Multi paradigm
Imperative, OOP, functional programming in one language.
Pro Great metaprogramming features
There are generics, templates, macros in Nim. They can allow you to write new DSL for your application, or avoid all boilerplate stuff.
Pro Type interferencing
You only need to specify types in your procedures and objects - you don't need to specify type when you're creating a new variable (unless you're creating it without initialization)
Pro Has built-in unittest module
With built-in "unittest" module you can create test with a very readable code
You don't need to deal with all those manual memory allocations, Nim can take care of it!
But also you can use another GC, or tweak it for you real-time application or a game
Pro Easy to integrate with another languages
You can use Nim with any language that can be interfaced with C.
There's a tool which helps you to create new C and C++ bindings for Nim - c2nim
Pro Compile-time execution
Nim has built-in VM, which executes macros and some other code at compile time.
For example - you can check if you're on Windows, and Nim will generate code only for it
Pro Supports UFCS (Unified Function Call Syntax)
writeLine(stdout, "hello") can be written as stdout.writeLine("hello")
proc add(a: int): int = a + 5 can be used like 6.add.echo or 6.add().echo()
Pro Has built-in async support
Nim has "asyncdispatch" module, which allows you to write async applications.
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.
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 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 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.
Con Still in pre 1.0
Not very stable and has a rather small community.
Con All exceptions must be caught
The compiler enforces this, so code is littered with
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 Limited tooling
There's no IDE. Debuggers are fairly basic. Pony is too young to have much of an ecosystem.
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 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.