I started writing with Nim a couple years ago and I pretty much only write Nim code now. It’s such a joy to work with. Projects end up being much simpler. Getting out of the object oriented programming mindset helped a lot as well.
@Aditya, You are doing more to promote Nim then I am hearing from the nimmers, at least in the twitterverse ;) It would be interesting to hear your opinion on Jai because it has fast compiler (faster than Nim) and comp.time allowing type introspection and running games in the same time. Closed beta now but videos are in Jonathan Blow youtube.
Jai lacks the memory&resource management story and it's always easy to compile faster by leaving out compile-time checks or elaborate type inference. Nim compiles fast without cheating and will compile much faster in the future thanks to an improved compiler architecture, not thanks to leaving out dozens of useful features such as RAII.
@@andreasrumpf9012 Hey Andreas- nice work on nim! It looks like a really awesome language. I seem to be having some compilation slowness on my machine however and as I'm new to the language I don't know if it's "supposed" to be this way or if there is something wrong with my setup. I have minGW on windows and am using the 1.9.1 nightlies version. A simple script that doesn't do much takes about 3 seconds total to compile and run. I don't think it's supposed to take so long. It's just a little distracting as I am in the learning phase and am constantly modifying and recompiling scripts to test things out. Any advice or links/articles about how to going about resolving the issue would be much appreciated.. thanks!
Mh, that stuff about static introspection and compile time evaluation sounds a lot like D. 19:17 But could a macro not also create the extended type PersonV1 to eliminate copy&paste? 30:30 Ouuh, Implicit copies are dangerous. Copying should be an opt-in feature, not an opt-out. It's one of the defaults Rust got absolutely right.
I started writing with Nim a couple years ago and I pretty much only write Nim code now. It’s such a joy to work with. Projects end up being much simpler. Getting out of the object oriented programming mindset helped a lot as well.
Great presentation! Interesting to see so much focus on ARC and C++ interoperability
Love talks from Aditya Siram :)
@Aditya, You are doing more to promote Nim then I am hearing from the nimmers, at least in the twitterverse ;)
It would be interesting to hear your opinion on Jai because it has fast compiler (faster than Nim) and comp.time allowing type introspection and running games in the same time. Closed beta now but videos are in Jonathan Blow youtube.
Jai lacks the memory&resource management story and it's always easy to compile faster by leaving out compile-time checks or elaborate type inference. Nim compiles fast without cheating and will compile much faster in the future thanks to an improved compiler architecture, not thanks to leaving out dozens of useful features such as RAII.
@@andreasrumpf9012 Hey Andreas- nice work on nim! It looks like a really awesome language.
I seem to be having some compilation slowness on my machine however and as I'm new to the language I don't know if it's "supposed" to be this way or if there is something wrong with my setup.
I have minGW on windows and am using the 1.9.1 nightlies version. A simple script that doesn't do much takes about 3 seconds total to compile and run. I don't think it's supposed to take so long. It's just a little distracting as I am in the learning phase and am constantly modifying and recompiling scripts to test things out.
Any advice or links/articles about how to going about resolving the issue would be much appreciated.. thanks!
I'm honestly not sure what the value of the sink is, if nim just ignores it by default
AMAZING TALK!
Really cool and interesting talk
Terrific presentation… A little over my head but the stretch felt good :-)
Mh, that stuff about static introspection and compile time evaluation sounds a lot like D.
19:17 But could a macro not also create the extended type PersonV1 to eliminate copy&paste?
30:30 Ouuh, Implicit copies are dangerous. Copying should be an opt-in feature, not an opt-out. It's one of the defaults Rust got absolutely right.
Copies might be dangerous if want the speed. Otherwise it gets out of your way right?
@@EdubSi What if you modify the copy thinking you where modifying the original?
Really nice👍