News for hackers. Stuff that matters.
Re:Nimony: A New Compiler for Nim by netbioserror on Tuesday November 17, 2026 @09:22AM (#50531779)
It has a scoped responsibility, does mostly compute and data processing. Invoked by a PHP backend, single-threaded, we get parallelism at invocation rather than internally. So we can saturate server threads optionally if we need to.

Biggest win: Single-owner scoped lifetimes by default with no annotations plus expression-oriented value semantics makes it eminently readable. Basically no memory semantics, all business logic. (It does processing of proprietary binary data including a lot of math.) Extraordinarily easy to maintain, refactor, add features. Valgrind confirms no orphaned blocks in some of our biggest test scenarios, it's impressive. Full compile-time evaluation is nice too, easy to slurp a whole file at compile-time and have it accessible in a normal binding, writing generic procedures is obvious and simple.

Biggest pain point: Hard to say, the only friction I've really ever run into is its weak tooling. I just use Make for builds (invoking the compiler directly instead of using Nimble) and Sublime's built-in features for refactoring. It's small enough that print-debugging works, but I occasionally dip into FlameGraph. Nimsuggest has some...dealbreaking quirks, but successors are in the works.

Re:Nimony: A New Compiler for Nim by sirtaj on Tuesday November 17, 2026 @02:06PM (#50536531)
What are the biggest things you miss from the standard and third party libraries?
Re:Nimony: A New Compiler for Nim by netbioserror on Tuesday November 17, 2026 @02:59PM (#50537258)
1) From std, a fully Nim-native tiny regex engine (the tinyre package fills this need, and I think it should be the default; the default regex engine brings in PCRE as a dependency).

2) From std, compression (I pull the zippy package as a dependency, and have built against Brotli and other compression libaries; whether compression should be in std is I think something Araq may have commented on).

Aside from that, nothing. Nim's compiler has an extraordinarily powerful templating engine built-in called Source Code Filters: These build text replacement procedures at compile-time, and can handle most arbitrary Nim code, including generics and the compile-time `when` conditional, although certain sugary arrangements by the default parser can't work (Nim code in SCF must be prepended with a # to mark it, and control flow blocks must have end markers).