Something I find quite interesting about Nim is write tracking: http://nim-lang.org/blog/writetracking.html . It uses the language's effect system, and allows not only specifying for instance that a function is referentially transparent, but also specifying how an impure function accesses or modifies global state. An example from the above link: var gId = 0 proc genId(): natural {.writes: [gId].} = gId += 1 return gI…
Nim (formerly Nimrod) 0.10.2 released
21–30 of 149 posts
Re: Nim (formerly Nimrod) 0.10.2 released
#22Earlier quoted context omitted.
There is no technical reason why Rust should be slower than Nim, as far as I know.
Nim has the advantage of compiling to/through C, for which compilers have been optimized for a long time.
Re: Nim (formerly Nimrod) 0.10.2 released
#23Why did they change the name?
Although it honestly wouldn't surprise me if the difference between typing three or five characters to compile is a huge deal in programmer land. Just like how a few tenths of a second of extra loading makes an enormous difference in customer satisfaction with the Google:
http://www.nytimes.com/2012/03/01/technology/impatient-web-u...
Re: Nim (formerly Nimrod) 0.10.2 released
#24Earlier quoted context omitted.
There is no technical reason why Rust should be slower than Nim, as far as I know.
Nim has the advantage of compiling to/through C, for which compilers have been optimized for a long time.
Not to start a language flamewar but I'd like to see hard numbers before I believe that in the general case Nim is faster than Rust.
Re: Nim (formerly Nimrod) 0.10.2 released
#25I really like that change. Those always looked so archaic to me.
Re: Nim (formerly Nimrod) 0.10.2 released
#26Earlier quoted context omitted.
Nim has the advantage of compiling to/through C, for which compilers have been optimized for a long time.
Rust uses LLVM as a backend so it gets similar optimization passes as clang for instance, so it's not so different. Basically rustc generates LLVM IR where Nim generates C, apparently. In most of the benchmarks I've seen so far you could expect similar performances between C and Rust. Not to start a language flamewar but I'd like to see hard numbers before I believe that in the general case Nim is faster than Rust.
Re: Nim (formerly Nimrod) 0.10.2 released
#27Re: Nim (formerly Nimrod) 0.10.2 released
#28All the hype on HN seems to be towards Rust and Go (with Go having its share of haters), but Nim sounds particularly interesting as a side-step from Python that runs faster than both Go and Rust. Can anyone give me some insight as to why it's not as hyped, if at all? I'm rather unfamiliar with Nim, and it's seems to have a smaller community, but it feels like it should be getting all sorts of love considering its spe…
I've never used Nim and I should probably give it a try but it seems that the "garbage collected, parallel oriented" niche is somewhat more cluttered with the likes of Go, the various languages built on top of .Net or the JVM, the lisps, the haskells... Not all target exactly the same use cases but there's a lot of overlap here and it's harder to stand out.
Re: Nim (formerly Nimrod) 0.10.2 released
#29Earlier quoted context omitted.
Rust uses LLVM as a backend so it gets similar optimization passes as clang for instance, so it's not so different. Basically rustc generates LLVM IR where Nim generates C, apparently. In most of the benchmarks I've seen so far you could expect similar performances between C and Rust. Not to start a language flamewar but I'd like to see hard numbers before I believe that in the general case Nim is faster than Rust.
Have you seen these benchmarks? https://github.com/logicchains/LPATHBench/blob/master/writeu...
Re: Nim (formerly Nimrod) 0.10.2 released
#30Maybe it's just me but I find this language pretty ugly. And regardless of any technical advantages it may offer, that's enough reason to not use it. There's too many languages out there to come out with a new one where the code isn't clean and nice.