Re:Nimony: A New Compiler for Nim
by stakhanov on Tuesday November 17, 2026 @09:39AM
(#50532014)
I think it's all about corpus weight.
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, ratheer than keep two versions of the ecosystem going.
Re:Nimony: A New Compiler for Nim
by ghshephard on Tuesday November 17, 2026 @12:51PM
(#50535314)
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.
Re:Nimony: A New Compiler for Nim
by Beretta_Vexee on Tuesday November 17, 2026 @10:07AM
(#50532389)
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.
Re:Nimony: A New Compiler for Nim
by ghshephard on Tuesday November 17, 2026 @12:48PM
(#50535255)
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.
Re:Nimony: A New Compiler for Nim
by jibalt on Tuesday November 17, 2026 @10:54PM
(#50541673)
No. a) Python had vastly more users. b) That change hit things that were much more "mainstream" in the language, like string encoding and print as a function vs. a statement.
Re:Nimony: A New Compiler for Nim
by ModernMech on Tuesday November 17, 2026 @09:36AM
(#50531957)
Feels like a lot of these people haven't lived through or don't remember the days when every other blogs was the default wordpress theme, or if they got really creative, some other wordpress theme.
Re:Nimony: A New Compiler for Nim
by badsectoracula on Tuesday November 17, 2026 @04:00AM
(#50529115)
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).
Re:Nimony: A New Compiler for Nim
by pietroppeter on Tuesday November 17, 2026 @06:40AM
(#50530127)
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
Re:Nimony: A New Compiler for Nim
by flykespice on Tuesday November 17, 2026 @04:16PM
(#50538305)
IIRC, ref counting is at least more deterministic than traditional GC because it only runs when you destruct the object (it goes out scope, object gets reassigned whatnot).
In Comparison, traditional GCs like JVM runs on a background thread, it's hard to determine when they run and generally blocks the whole program while collecting (stop-the-world).
So at least they are a little better in that regard?
Re:Nimony: A New Compiler for Nim
by vips7L on Tuesday November 17, 2026 @10:56PM
(#50541692)
I can’t speak of Nim’s implementation but reference counting can block the whole program as large object graphs have to decrement their counts. But you are right it is more deterministic.
Javas modern GCs also have extremely low pauses. ZGC is effectively pauseless, you’re likely to experience kernel jitter/traps that last longer than a ZGC pause.
Re:Nimony: A New Compiler for Nim
by flykespice on Wednesday November 18, 2026 @07:39AM
(#50545583)
Does it suffer from the same trap as Dlang, in that their GC is also optional, but you lose the many of the conveniences from the standard library if you forgo completely with it?
Re:Nimony: A New Compiler for Nim
by Gesee on Wednesday November 18, 2026 @07:52AM
(#50545719)
GC is optional in the sense "don't use `ref` types and there will be no GC"
Value types (`object`) use mutable value semantics and scope based destructors, so there are safe without GC
Re:Nimony: A New Compiler for Nim
by jphoward on Tuesday November 17, 2026 @04:19AM
(#50529214)
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.
Re:Nimony: A New Compiler for Nim
by ZoomZoomZoom on Tuesday November 17, 2026 @04:59AM
(#50529474)
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)`.
Re:Nimony: A New Compiler for Nim
by PMunch on Tuesday November 17, 2026 @06:11AM
(#50529934)
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.
Re:Nimony: A New Compiler for Nim
by klibertp on Tuesday November 17, 2026 @07:57PM
(#50540481)
As others wrote, what makes it unpalatable for you is static typing. You simply cannot make working with arbitrary JSON as convenient in a statically typed language as in a dynamic language (like JS or Python). No matter what you do, in a static language you need to provide or recover/generate the full type information of anything before you can use it (unless the language or the runtime system offers an escape hatch: some kind of "dynamic" type (but that means the language is now gradually typed) or strong reflection capabilities - which Nim doesn't provide to my knowledge). On the other hand, Nim has macros, so typing your JSON payloads is as painless as it can possibly be in the presence of static types.
So it's not really Nim's characteristic to make working with arbitrary JSON (heterogeneous collections more generally) "unpalatable" - it's common to (almost) all statically typed languages. While Nim looks a lot like a scripting language, it really isn't. It can be used as one, and it's much better for that than C, but it's better used for apps and systems programming than for scripting, like all the other languages in its class (ie. Go, Crystal, OCaml; Rust and Java are also close).
Re:Nimony: A New Compiler for Nim
by stakhanov on Tuesday November 17, 2026 @05:28AM
(#50529666)
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.
Re:Nimony: A New Compiler for Nim
by pietroppeter on Tuesday November 17, 2026 @06:45AM
(#50530160)
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)
Re:Nimony: A New Compiler for Nim
by raffraffraff on Tuesday November 17, 2026 @09:14AM
(#50531668)
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"
Re:Nimony: A New Compiler for Nim
by tokai on Tuesday November 17, 2026 @09:41AM
(#50532039)
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.
Re:Nimony: A New Compiler for Nim
by pietroppeter on Tuesday November 17, 2026 @12:34PM
(#50535020)
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).
Re:Nimony: A New Compiler for Nim
by afavour on Tuesday November 17, 2026 @09:00AM
(#50531471)
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.
Re:Nimony: A New Compiler for Nim
by Gesee on Wednesday November 18, 2026 @04:58AM
(#50544235)
I don't think we can call that transpilation as it's not a 1:1 conversion
But yeah, the native backend and LLVM backend definitively close the "transpilation" door
Re:Nimony: A New Compiler for Nim
by elcritch on Tuesday November 17, 2026 @12:38PM
(#50535092)
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.
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 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).
Re:Nimony: A New Compiler for Nim
by deepsquirrelnet on Tuesday November 17, 2026 @09:30AM
(#50531880)
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.
Re:Nimony: A New Compiler for Nim
by trueno on Tuesday November 17, 2026 @09:50PM
(#50541246)
yea nim is fuggin awesome i tried it this year too and ive seen enough python that it just felt straight forward. i lurv me some compiled stuff and everything ive built in nim does not disappoint on the performance front. i love using it honestly, feels like what i always wished python was
Re:Nimony: A New Compiler for Nim
by lcnmrn on Tuesday November 17, 2026 @09:32AM
(#50531903)
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
Re:Nimony: A New Compiler for Nim
by Gesee on Wednesday November 18, 2026 @06:32AM
(#50545012)
No need for that, I checked it, it's a good little language but not near Rust or Nim
The way you designed bound checking, parameter inferences is more a source of bugs than anything
I didn't see support for advanced closures and how it's integrated with the borrow checker (since you claim not having lifetimes, there are tons of unanswered questions in your thing)
Your desing of generic instantiation is just a compile time pit.
You don't constraint type so you need to check the body of every instance
You have NLL yeah, but not partial borrows nor the capacity for a proc to return one of it's parameters (the famous example
```rs
fn longest<'a>(x: &'a str, y: &'a str) -> &'a str {
if x.len() > y.len() { x } else { y }
}
```
since you don't have lifetimes, either you refuse this case or it's a bug
if you do a copy then your language asks it's user to use value semantics
But if your language mostly push users to value semantics (a.k.a copying tons of things) then why all the borrow stuff ? If there is no lifetime how is one suposed to store references ? why is there a ref, ref_mut type ?
Those are overly convoluted choices for a value based language
So it's a bit of an incoherence
Next there is the way you handle indexing
your spec state that undecided index access generate stricta_bounds_fail, but this function just output an error and exit the process, it doesn't insert a runtime check
So undecided index access act as nuke in the codebase, the users is not even aware that one of it's access is undecided, and when he expect it the less he just get the process stopped, no exceptions, just a crash
Then you don't even correctly handle cyclic data type structure, you defined in the codebase an arbitrary depth of 16 instead of checking type cycle (and what you stated in your spec just worked auto referencing types like type A with a field of type A again
Re:Nimony: A New Compiler for Nim
by Symmetry on Tuesday November 17, 2026 @09:52AM
(#50532171)
> 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.
Re:Nimony: A New Compiler for Nim
by shevy-java on Tuesday November 17, 2026 @11:46AM
(#50534162)
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?
Re:Nimony: A New Compiler for Nim
by sergiotapia on Tuesday November 17, 2026 @12:07PM
(#50534536)
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.
Re:Nimony: A New Compiler for Nim
by tokai on Tuesday November 17, 2026 @02:17PM
(#50536702)
I have a hobby nim project at about 22K LOC, stdlib only. A quick and naive llm rewrite to nimony gave a ×1.3 runtime speed up. Pretty cool, will definitely keep up on nimony's development.
Re:Nimony: A New Compiler for Nim
by flykespice on Tuesday November 17, 2026 @04:44PM
(#50538648)
I have been eyeing nim for a while though I more used to curly-braced language families.
The first thing I evaluate in a language is how it looks like in production code, and the samples in github strikes me odd -- like most of the code identation is 2-space and no line break between variable declaration and ifs/else (everything is lumped together).
Sum-types, borrow-checking... Nim 3 is beautiful.
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, ratheer 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.
Just like when HTML templates started to be a business all websites looked the same.
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).
This is bad for accessibility, bad for compatibility, and serves no purpose at all.
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
The big question is naturally the adoption curve, given the breaking changes.
https://nim-lang.org/docs/mm.html
In Comparison, traditional GCs like JVM runs on a background thread, it's hard to determine when they run and generally blocks the whole program while collecting (stop-the-world).
So at least they are a little better in that regard?
Javas modern GCs also have extremely low pauses. ZGC is effectively pauseless, you’re likely to experience kernel jitter/traps that last longer than a ZGC pause.
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
So it's not really Nim's characteristic to make working with arbitrary JSON (heterogeneous collections more generally) "unpalatable" - it's common to (almost) all statically typed languages. While Nim looks a lot like a scripting language, it really isn't. It can be used as one, and it's much better for that than C, but it's better used for apps and systems programming than for scripting, like all the other languages in its class (ie. Go, Crystal, OCaml; Rust and Java are also close).
Thanks, Andreas Rumpf, for sticking with it for all these years: This seems like a great opportunity for me to get back into nim.
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!
- https://nimony.org/stdlib/std/result.html
- https://nimony.org/stdlib/std/options.html
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.
The modern embedded devices that still only get Assembly and C toolchains are like PIC class devices.
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, 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.
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).
There is either a catch here or you(r LLM) has solved multiple open research problems.
Your desing of generic instantiation is just a compile time pit. You don't constraint type so you need to check the body of every instance
You have NLL yeah, but not partial borrows nor the capacity for a proc to return one of it's parameters (the famous example
```rs
fn longest<'a>(x: &'a str, y: &'a str) -> &'a str { if x.len() > y.len() { x } else { y } }
```
since you don't have lifetimes, either you refuse this case or it's a bug if you do a copy then your language asks it's user to use value semantics
But if your language mostly push users to value semantics (a.k.a copying tons of things) then why all the borrow stuff ? If there is no lifetime how is one suposed to store references ? why is there a ref, ref_mut type ?
Those are overly convoluted choices for a value based language So it's a bit of an incoherence
Next there is the way you handle indexing your spec state that undecided index access generate stricta_bounds_fail, but this function just output an error and exit the process, it doesn't insert a runtime check
So undecided index access act as nuke in the codebase, the users is not even aware that one of it's access is undecided, and when he expect it the less he just get the process stopped, no exceptions, just a crash
Then you don't even correctly handle cyclic data type structure, you defined in the codebase an arbitrary depth of 16 instead of checking type cycle (and what you stated in your spec just worked auto referencing types like type A with a field of type A again
No thanks.
I've never been too annoyed by Nim's approach but I think this removes a complaint many people have.
The first thing I evaluate in a language is how it looks like in production code, and the samples in github strikes me odd -- like most of the code identation is 2-space and no line break between variable declaration and ifs/else (everything is lumped together).
Just check https://github.com/WyattBlue/auto-editor/blob/master/src/wav... to have an idea of what I'm talking about. Is that how normal nim code supposed to look like? (following its best practices)