I can't believe this has not been linked yet: https://nim-lang.org/blog/2020/10/16/version-140-released.html
Hacker news post and discussion: https://news.ycombinator.com/item?id=24800161
Reddit post and discussion: https://www.reddit.com/r/nim/comments/jcdbvu/nim_version_140_released/
Congratulations to everyone who contributed.
New ORC thing is awsome!
Here is leorize comment that explains what is going on.
Nim's current async implementation creates a lot of cycles in the graph, so ARC can't collect them. ORC is then developed as ARC + cycle collector to solve this issue, and it has been a success. This 1.4 release introduces ORC to everyone so that we can have mass testing for this new GC and eventually move torwards ORC as the default GC.
The source tarball linked on the website doesn't seem to be right. There are already binaries in the bin directory and no build.sh script.
The source tarball linked on the website doesn't seem to be right.
That's why we didn't want to announce it on the forum just yet (until @treeform ruined our tactic ;)); we're working on a fix.
In the mean time, you can grab source tarballs from this link: https://github.com/nim-lang/nightlies/releases/tag/2020-10-16-version-1-4-018ae963ba83934a68d815c3c1c44c06e8ec6178
Thank you and a big thank to all contributors!
Unfortunately, as you can see, we messed up this release a bit. Reason: We had a couple of solid releases, fully automated, grew confident, did the same steps this time but the "nightly builds" setup was changed. :-)
I started a thread some time ago to keep track of ideas to improve the front page: https://forum.nim-lang.org/t/6740
Unfortunately I've not found the time to spend on actually making a PR to nim-lang/website to update the wording.
Go was a consideration and there are a few libraries internally existed for Go at that point, but nim in the end won out on acceptance and it convinced - despite the known risks of using a only semi-mature language - on feasibility in getting it done in time for the initial game release.
The PoC was incredibly quick to manifest, and iterating on it had quickly proven itself as a good way forward.
Peace of mind was a judgment call. Despite being a rather sizeable project now, what we had back then was already very stable and reliable (even under heavy benchmark load) and there weren't any great unknowns souring making the call.
Go code runs much more slowly than Nim code in my experience. Nim realizes better ergonomics than Python in some ways (UFCS, command syntax, user-defined operators) and as good performance & lightweightness as C/Rust.
I'm honestly surprised Nim is not the secret weapon of many start-ups. Nim is much more "open architecture" instead of pushing some "single, canned turn-key fits most users" solutions.
Having a juggernaut like Google marketing/pushing/subsidizing something might provide false as well as true peaces of mind. :-) { Such peace is a multi-dimensional concept. :-) }
I don't speak English but it reflects what I think about hacker new.
Thanks to the team-nim
Grand Merci à l'Équipe-Nim
Just a small thing maybe but immensely valuable for me: From v. 1.4 on we finally have a 'compile' pragma with a "built-in local passC" - and it works well and nicely.
What a beauty, so yet another big THANK YOU! to @Araq and the team! If I were less ugly I'd even offer to kiss you on your foreheads g