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.
> Nimony is case sensitive like most other modern programming languages. The reason for this is implementation simplicity. This might also be changed in the future.
I've never been too annoyed by Nim's approach but I think this removes a complaint many people have.
I am not sure. I think Nim is a fine language, but it is a little bit cumbersome as well, due to the typing. People complain just about everything, so this is not a good metric to use as the only metric. Nim has a similar problem as crystal has: too few users. With the rise of AI, this problem has amplified. You can see it if you look at Ruby, how it declined in the last two years. I wonder what young people do these days. Has learning programming languages become worse here?
I’m curious if this closes the door on Nim’s capability to output C code which you then compile yourself. I first discovered Nim when I was looking for something that could work with Apple’s requirements to embed bitcode in iOS apps, it meant you had to use their specific version of LLVM and that ruled out a lot of languages. It always seemed like a really unique feature (though IIRC Haxe has something similar).
Apple has long since removed that requirement so it doesn’t really matter anyway and I wouldn’t blame the Nim folks if it’s gone, these seem like a great set of improvements.
This is a great part of Nim. I started using it with ESP32's for 5+ years or so now. Nimony is even more ideal for embedded.
Great part is that Nim's stdlib networking was easy to port to esp-idf's lwIP based network stack. So you get access to production Nim libraries for lots of networking stuff, or async, etc.
I did my first "real" nim project this year. I'd been tinkering with it here and there, but found a chance to use it. I'm coming from mostly python experience and found it to be a really nice experience.
When Python did the migration, it had a good flow of new investments coming into it and delivered good reasons for why those should go to Python 3 rather than 2. At the same time, it also already had a base of existing investments in Python 2 delivering better ROI without the added cost of a migration, and the sum of that exceeded the critical mass it took to make it economical to keep both versions of the ecosystem around.
With Perl you are seeing what it looks like when you have zero new investments coming in and no good reasons for why new investments should go to Raku. (Because: Just use Python). You do still have a non-negligible base of existing investments in Perl 5 and those deliver better ROI without the added cost of a migration. So my prediction is that Perl 5 will stick around, and Raku is dead on arrival.
With Nim it might be the other way around: Good reasons for why new investments should go to Nim 3 rather than Nim 2, and not all that much existing investment in Nim 2. If Nim 3 sees healthy adoption, it might well be more economical to re-deploy ecosystem maintenance to Nim 3 and migrate most of the existing code, rather than keep two versions of the ecosystem going.
I know you realize this, but it is worth emphasizing that Perl 5 vs Perl 6 is a not comparable to Python 2 to Python 3. For 98%+ of code, Python 2 and Python 3 are mostly identical, and the conversion, even in massive code-bases, is completely mechanical for 99.5% of the code.
It was largely a question of the existing codebase. It took years to convert all the obscure scientific libraries from Python 2 to Python 3.
The migration was no easy task. So all the projects already written in Python 2 remained on version 2. Until the day they reached a dead end and were forced to migrate.
It was inertia. I was working at a company in 2017 in which 100% of the very extensive code base was written in Python2. The Python3 migration was done in a weekend and was mostly a nothing burger, as, with few exceptions, the conversion was 100% mechanical and just worked. The print vs print() was the most visible change, and the str/bytes change was a genuine improvement.
Except for no longer being confused about whether I was reading bytes or "strings" (Python3 eliminated that confusion), and having to remember for roughly a year to use "()" when using print, I don't believe I even really noticed that big a difference between the two.
Honestly - I'm surprised that python managed to hold on long enough for "uv" to be released and solve all the packaging/venv pain - that was a real problem with python for 15+ years and wasn't solved until 2024.
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)
I thought it would be the opposite, because you can't say: "The AI was trained on a bazillion lines of idiomatic Nim 3 solving a wide range of common problems"
Yep that is the expectation one could have but it is not the experience I (and many others) had.
The explanation I have is that it is so close to pseudocode that it only needs to know just a tiny bit about Nim peculiarities (not too many) to do a good job (plus static types and compiler help a lot).
Ai writes nim pretty well. Its close enough to other languages that llms can manage to write performant code with few issues. There are some gotchas, but the fast compile times and good error messages makes it easy to iterate fast for the bots.
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?
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 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)`.
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, and 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 build scripting (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.
I've always had a soft spot for Nim, never had the chance to use it professionally. I personally can't wait to let it rip with AI. I think this is going to be the perfect language to use with AI. Fast as all holy hell, ergonomic, a language lead who cares deeply and does not quit. Major props to Araq for sticking it through all these years, I hope it's Nim's time to shine finally.
ref counting is only performed if you use `ref` types, e.g.
type
RefObj = ref object
foo: string
bar: int
ValueObj = object
foo: string
bar: int
`RefObj` is ref counted equivalent to a shared_ptr in C++ land (non-atomic counter unless using --mm:atomicArc or Nim3/Nimony has this as a default I believe). `ValueObj` is equivalent to struct in C, C++, etc.
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.)
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).
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
This feels archaic to me after seeing what is possible with Stricta. You get full Python syntax as low level as possible, safe, strict, no ARC/GC, memory access. https://github.com/lucianmarin/stricta
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've never been too annoyed by Nim's approach but I think this removes a complaint many people have.
Apple has long since removed that requirement so it doesn’t really matter anyway and I wouldn’t blame the Nim folks if it’s gone, these seem like a great set of improvements.
Great part is that Nim's stdlib networking was easy to port to esp-idf's lwIP based network stack. So you get access to production Nim libraries for lots of networking stuff, or async, etc.
Sum-types, borrow-checking... Nim 3 is beautiful.
Check how many deployments (products even) are still being done in Java 8, or .NET Framework.
When Python did the migration, it had a good flow of new investments coming into it and delivered good reasons for why those should go to Python 3 rather than 2. At the same time, it also already had a base of existing investments in Python 2 delivering better ROI without the added cost of a migration, and the sum of that exceeded the critical mass it took to make it economical to keep both versions of the ecosystem around.
With Perl you are seeing what it looks like when you have zero new investments coming in and no good reasons for why new investments should go to Raku. (Because: Just use Python). You do still have a non-negligible base of existing investments in Perl 5 and those deliver better ROI without the added cost of a migration. So my prediction is that Perl 5 will stick around, and Raku is dead on arrival.
With Nim it might be the other way around: Good reasons for why new investments should go to Nim 3 rather than Nim 2, and not all that much existing investment in Nim 2. If Nim 3 sees healthy adoption, it might well be more economical to re-deploy ecosystem maintenance to Nim 3 and migrate most of the existing code, rather than keep two versions of the ecosystem going.
Perl 5 and Perl 6 (Raku) are different languages.
The migration was no easy task. So all the projects already written in Python 2 remained on version 2. Until the day they reached a dead end and were forced to migrate.
Except for no longer being confused about whether I was reading bytes or "strings" (Python3 eliminated that confusion), and having to remember for roughly a year to use "()" when using print, I don't believe I even really noticed that big a difference between the two.
Honestly - I'm surprised that python managed to hold on long enough for "uv" to be released and solve all the packaging/venv pain - that was a real problem with python for 15+ years and wasn't solved until 2024.
- https://nimony.org/stdlib/std/result.html
- https://nimony.org/stdlib/std/options.html
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)
The explanation I have is that it is so close to pseudocode that it only needs to know just a tiny bit about Nim peculiarities (not too many) to do a good job (plus static types and compiler help a lot).
Planetis also provides commercial skills experimentally verified to work with Claude/Codex/etc models for a small monthly fee!
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.
So it’s really the case that JS conflates objects/dictionaries, so only people familiar with only JS would know what you mean
Edit: actually thinking about it, I’m fairly positive python also models objects as dictionaries; it just puts more effort into hiding it
Biggest pain point? Biggest win?
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, and 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 build scripting (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.
The big question is naturally the adoption curve, given the breaking changes.
https://nim-lang.org/docs/mm.html
This is bad for accessibility, bad for compatibility, and serves no purpose at all.
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).
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..
this gives the design a cheap ai-template vibe
Just like when HTML templates started to be a business all websites looked the same.
There is either a catch here or you(r LLM) has solved multiple open research problems.
No thanks.