When comparing Pony vs Zig, the Slant community recommends Zig 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?” Zig is ranked 18th while Pony is ranked 22nd. The most important reason people chose Zig is:
It's safer than C, at least.
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 Some safety
It's safer than C, at least.
Pro C Interop
Zig programs can import C libraries and export header files to be used in C programs.
Pro Performance
Zig is pretty fast, in some cases even faster than C.
Pro Cross-compilation is easy
The Zig compiler can build artifacts for any Tier 3 Supported platform without additional downloads.
Pro Control flow is simple and obvious
No operator overloading, property methods, runtime dispatch, macros, etc.
Pro Small binary
Produces binary smaller than C.
Pro Compile-time execution
Zig can execute code at compile-time, allowing for more performant and readable programs.
Pro No Hidden Control flow
Zig will not do anything on your back that might slow down your program & make you loose your control over your program.
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 Convoluted syntax
Claims to be an improvement over C, but in this area, not really.
Con No lambdas
Missing many key and useful features other languages have.
Con Deceptively gives impression it's near being production ready
No plans to hit 1.0 until 2025 (3 years later), according to Zig Roadmap speech. Impression is given that (0.9.1) language was close to ready, when it's not.
Con Creator admits to not knowing what he's doing
Creator admits his shortcomings during Zig Roadmap speech. Very disturbing. Not a language to invest in or take seriously, outside personal experimentation.
Con No closures
Does not have closures.
Con Almost no community
Lacking in libraries and users.
Con No interfaces/traits
Features that are useful are missing, where you can find them in other languages.
Con Fundraising looks suspicious
Why do we keep seeing an overhyped unfinished alpha level language showing up everywhere? That answer looks like a financial incentive to promote the language, the Zig Software Foundation, that is making hundreds of thousands of dollars a year from donations. To aggressively maintain cash flow, it appears any opinions that goes against their narrative is suppressed, attacked, or eliminated. All while the hype machine runs rampant. That isn't a language for the people, that looks to be a cash grab for the few that will result in nothing useful. Save yourself the headache and games, better to just use C or other languages with C-like syntax, can interface with C, and are actually useful. Better to not waste your valuable time on crap like Zig, false media hype, or getting scammed.
”If it sounds too good to be true, it probably is.”
This blog has published 2 excellent articles on how Zig's claims do not live up to reality after more than 6 years of development.
Con Poor compiler errors
Several years into development, language still a mess, and no hope of fixing itself for yet more years later.
Con No standard package manager
Several years into development, and still no standard package manager is ridiculous.
Con Exhibits cult-like behavior and animosity towards other programming languages
Strange culture that bashes other languages and are not open to criticism about the faults of their language. Very close-minded, sometimes scary.
