When I was doing the rounds roughly 10 years ago, trying to find a new programming language to learn, my money for "next big thing" landed on nim. I did some personal projects and absolutely loved it but, unfortunately, opportunities to work "on the clock" in nim never materialised and then rust started eating the world.
Thanks, Andreas Rumpf, for sticking with it for all these years: This seems like a great opportunity for me to get back into nim.
I love Nim but my only problem with it previously was support for dictionaries/objects felt really weird? There was some sort of JSON structure as I recall, but it didn't seem anywhere near as easy to use as the analogous structures in Python/JS. Am I misremembering? Has this been improved?
I suspect you're talking about heterogenous containers which are antithetical to a strongly typed language but nevertheless are supported via std/json's JsonNode dynamic data.
In Nim regular hash maps (called tables here) have pretty regular accessors via `[]` `[]=` overloads (`foo["frob"]=42`), plus additional routines such as `.get(otherwise)`.
Nim is very strict about types, which is probably what you remember. Things that are typically expressed as a dictionary/object in JavaScript and Python are better represented as a fully typed tree of objects in Nim. The language of course supports the data-structure dictionary/hashmap/table (called Table in Nim) which is "anything hashable" -> "any type" lookup. This is what's used for things like `myTable["hello"] = 5` for storing the number 5 for the key "hello". However because of the strict types you can't mix which types they map to without creating some sort of wrapper type that gives you the alternatives you're allowed to use. Many people reach for Nims JsonNode type to fill this gap for small collections of string/number/array/dictionary since it already is such a wrapper type.
I think Nim is a great fit for the AI era. let me explain
Always appreciated how Nim gives you a low cognitive load: it is easy to reason about, does not get in the way of doing stuff, you focus on what you need to do it and rarely on how you do it (specifics of the language).
I think this is a great advantage in this era of automatic/AI assisted programming. The fact that the language is very readable also helps for the moments when you need/want to read the code.
Nimony btw is a very cool way to evolve the mainline compiler and looking forward to use this in main Nim (but it is also something nice to experiment with)
Personally i like the site's design, it looks like from late 2000s / early 2010s with its gradient rounded buttons, 1px offsets and chiseled text - i even clicked randomly on buttons because of how "buttony" they look :-P.
IME this isn't what LLMs make by default, so if nothing else, i doubt it was a single prompt and most likely it was adjusted to fit the author's taste (that it sounds like doesn't align with yours).
Ha, that is bad. This is what happens when you use the cheap LLMs. (At least, I hope Opus 5.5 isn't pulling stunts that are this bad... It's not that bad when I look at my code.)
I think there was very little effort put on this specific website. The effort has gone in the compiler itself (and the mainline compiler). Not that it would not benefit for a better website
When I was doing the rounds roughly 10 years ago, trying to find a new programming language to learn, my money for "next big thing" landed on nim. I did some personal projects and absolutely loved it but, unfortunately, opportunities to work "on the clock" in nim never materialised and then rust started eating the world.
Thanks, Andreas Rumpf, for sticking with it for all these years: This seems like a great opportunity for me to get back into nim.
Nice, it looks like it supports option and result types as well:
- https://nimony.org/stdlib/std/result.html
- https://nimony.org/stdlib/std/options.html
It’s super exciting. It’s basically adding all the features I wished Nim had, and I’ve been using Nim in anger since the v0.10 days!
This is great! Congrats to the Nim team for keeping the pedal to the metal!
Sum-types, borrow-checking... Nim 3 is beautiful.
BTW, Sum types (along with incremental compilation, SSO strings and other thing) have been recently added to Nim 2 with the 2.4.0 release: https://nim-lang.org/blog/2026/10/28/nim-240.html
How does this differ from this new compiler?
Is this a Python 2/3 situation?
Might be, but Nim is statically typed, and we have LLMs now, so migration should be pretty trivial, is my guess.
Speaking from the stand of Java and .NET breaking changes, it is not, some folks will cling to the old world no matter what.
Check how many deployments (products even) are still being done in Java 8, or .NET Framework.
I love Nim but my only problem with it previously was support for dictionaries/objects felt really weird? There was some sort of JSON structure as I recall, but it didn't seem anywhere near as easy to use as the analogous structures in Python/JS. Am I misremembering? Has this been improved?
I suspect you're talking about heterogenous containers which are antithetical to a strongly typed language but nevertheless are supported via std/json's JsonNode dynamic data.
In Nim regular hash maps (called tables here) have pretty regular accessors via `[]` `[]=` overloads (`foo["frob"]=42`), plus additional routines such as `.get(otherwise)`.
https://nim-lang.github.io/Nim/tables.html
Don't know why are you conflating objects in your question.
I'm 'conflating' them because they're called objects in javascript, so people unfamiliar with Python know what I mean. Ok thanks.
Nim is very strict about types, which is probably what you remember. Things that are typically expressed as a dictionary/object in JavaScript and Python are better represented as a fully typed tree of objects in Nim. The language of course supports the data-structure dictionary/hashmap/table (called Table in Nim) which is "anything hashable" -> "any type" lookup. This is what's used for things like `myTable["hello"] = 5` for storing the number 5 for the key "hello". However because of the strict types you can't mix which types they map to without creating some sort of wrapper type that gives you the alternatives you're allowed to use. Many people reach for Nims JsonNode type to fill this gap for small collections of string/number/array/dictionary since it already is such a wrapper type.
I wonder if this is more palatable with first-class sumtypes/ADTs in Nim 3? Or is that already what JsonNode essentially was?
Hopeful for the new compiler but wished they'd called it Nimoy!
I think Nim is a great fit for the AI era. let me explain
Always appreciated how Nim gives you a low cognitive load: it is easy to reason about, does not get in the way of doing stuff, you focus on what you need to do it and rarely on how you do it (specifics of the language).
I think this is a great advantage in this era of automatic/AI assisted programming. The fact that the language is very readable also helps for the moments when you need/want to read the code.
Nimony btw is a very cool way to evolve the mainline compiler and looking forward to use this in main Nim (but it is also something nice to experiment with)
No i386? We do exist.
Does anyone already have experience, how the developer experience is? Error messages, debugging and so on?
Looking interesting, I like the improvements over what Nim used to be.
The big question is naturally the adoption curve, given the breaking changes.
It's not a big issue since Nim didn't have a large following. If anything, it might help Nim to take off if it's good enough and user friendly enough.
Only that the following might become even smaller.
Nim still has the GC, right? It always seemed like a slightly better Golang, much worse Dlang in that respect.
Optionally but not by default ... things have changed a lot:
https://nim-lang.org/docs/mm.html
Reference counting by default is GC.
Cool, now we can fight the borrow checker in Nim, too.
If I understand correctly, it still does have reference counting so you don't have to fight the borrow checker if you don't want to.
Nim is cool, but holy moly this web design is disgusting. Absolute one-shot prompting.
Not everything you dont like is LLM-made.
it's definitely LLM-made (if you look at the CSS, there's LLM-written comments) but it doesn't look like a one-shot prompt
Nowadays the brown background Claude design is everywhere, at least this one is somehow different.
Just like when HTML templates started to be a business all websites looked the same.
No, but this definitely is. https://github.com/nim-lang/nimony-website/commits/master/
idk, looks like a classic design from 2010. See QIP or AIMP Classic.
Everyone has a different taste.
Personally i like the site's design, it looks like from late 2000s / early 2010s with its gradient rounded buttons, 1px offsets and chiseled text - i even clicked randomly on buttons because of how "buttony" they look :-P.
IME this isn't what LLMs make by default, so if nothing else, i doubt it was a single prompt and most likely it was adjusted to fit the author's taste (that it sounds like doesn't align with yours).
What shockingly poor code. Just disgraceful.
This is bad for accessibility, bad for compatibility, and serves no purpose at all.
Ha, that is bad. This is what happens when you use the cheap LLMs. (At least, I hope Opus 5.5 isn't pulling stunts that are this bad... It's not that bad when I look at my code.)
It looks good on my phone and everything loads virtually instantly.
It has a clean theme. The only knock I can see is that the buttons are a little retro. But I like them .
Because of how fast every link loads and uncluttered the design is (not a single ad of any sort), I think it's better than 90% of websites.
The fact that your fashion sense weighs other trend aesthetics so much over those things..
border-left: 3px solid color...;
this gives the design a cheap ai-template vibe
I think there was very little effort put on this specific website. The effort has gone in the compiler itself (and the mainline compiler). Not that it would not benefit for a better website