31–40 of 121 posts
In what cases is Nim a better option than Rust? Would be great if anyone with more experience can share more information.
It provides the productivity of having a GC around (no need with coding for borrow checker patterns), you can still go as low level as you want, including writing GC free code, and is very fast compiling code.
Earlier quoted context omitted.
Nim compiles to js (as well as c and c++)
How much of C and the standard library does it use? Like, if I wanted to make my own C compiler, how much would I have to implement for it to be usable with Nim-generated code? Does it use a fairly constrained subset or does it use a lot of C and the standard library? I imagine the latter but just curious.
I think it's no longer maintained, but there's a kernel that boots on metal written in Nim. Furthermore, people are running Nim on ESP32, Nintendo Switch, JS (Browser, Node), iOS, Android and more; From that alone its clear that the C library can't be a significant dependency.
(And ... just about any C compiler around, including GCC, LLVM, TCC, MS C, Intel C, Zig C are supported when using C as a backend).
Too bad nim uses a whitespace-sensitive syntax like python, something I personally dislike.
Earlier quoted context omitted.
Nim compiles to js (as well as c and c++)
How much of C and the standard library does it use? Like, if I wanted to make my own C compiler, how much would I have to implement for it to be usable with Nim-generated code? Does it use a fairly constrained subset or does it use a lot of C and the standard library? I imagine the latter but just curious.
Too bad nim uses a whitespace-sensitive syntax like python, something I personally dislike.
Too bad nim uses a whitespace-sensitive syntax like python, something I personally dislike.
This might have been excused if they didn't also forbid tabs unless you use a hack ( https://github.com/nim-lang/Nim/wiki/Whitespace-FAQ#tabs-vs-... ), was interested in learning until I found this out
Too bad nim uses a whitespace-sensitive syntax like python, something I personally dislike.
You're free to use Golang or another language. Nim has a great feature set and will be a good fit for Python or Ruby teams wanting a more performant language. At the same time, it's more expressive than Golang and will fill a niche Golang couldn't meet. I like that we now have Golang, Rust, Swift, Nim, and Kotlin. They're all doing new things and excelling at their own niches.
Earlier quoted context omitted.
I consider Nim to be a compiled, faster Python. Nim is very easy to read and understand, and prototype in, vs. Rust.
Nim looks Pytonish (and has some Python-inspired syntax), but it is very much NOT Python. People coming from Python that expect a "compiled, faster" Python often find a compiled, faster language but have very weird concepts expecting that language to behave like Python though it isn't.
Too bad nim uses a whitespace-sensitive syntax like python, something I personally dislike.
That's actually one of it biggest advantages over the competition. I wish more languages cared about readability.
Python using whitespace doesn't allow me to mess up and have my formatter autoformat it. Js and others with {} have way too many symbols flying around for easy parsing.
Thats why I really like crystal! Do/end, low level, elegant. Wish the devs would focus more on wasm and other features that would put it more in the spotlight.
Too bad nim uses a whitespace-sensitive syntax like python, something I personally dislike.
You're free to use Golang or another language. Nim has a great feature set and will be a good fit for Python or Ruby teams wanting a more performant language. At the same time, it's more expressive than Golang and will fill a niche Golang couldn't meet. I like that we now have Golang, Rust, Swift, Nim, and Kotlin. They're all doing new things and excelling at their own niches.
Anyways, I'm just voicing my personal gripe with the use of whitespace-sensitive syntax. Nim is a overall a good language to use.