Nim is a fucking meme. I spent months on a huge project only to have the compiler update once and now it segfaults and I can't fucking figure out why. If you were considering using this piece of shit, stay away for a few more years until it stops being one. (And I have low hopes of this happening.)
>>52542724
>actually using a meme language
You should not brag about your own incompetence here...
>>52542724
>not using C, C++ or C#
top kek
>>52542801
>C++
>any year
>>52542787
It was actually really good until the latest updates
Segfaults are a meme now? I can't keep up 2015+1 is 2dank4me
>>52542801
>C
Just end up using high level libraries because C can't do shit without wasting hundreds of hours
>C++
lol
>C#
>Micro$haft
heh
>>52542813
>I know nothing about C++11 and C++14
Stay NEET boy.
>>52542847
>hey let's add more features to our already bloated language to make it better!
!
>>52542842
enjoy your segfaults ;^)
>>52542870
maybe I should have just used python
>>52542724
The compiler segfaults, or your code? If the latter, very probably you fucked up memory management somewhere and the old compiler/libraries were just more tolerant/you got lucky.
>>52543197
Nim handles memory management for you. The error message doesn't even give me a proper line, just the line where I declare the procedure. I probably did fuck up somewhere, but I'd really like to have a clue where.
>>52542842
what's bad about C#?
what other language would you suggest?
>>52543440
I'd honestly rather use C++ than C#. C# is basically java and that's all cancer. OOP is pretty much cancer too.
gdb
run [your program]
>>52543449
C# is much less bloated though and you still have the advantage of proper memory management.
would you use C++ for game development rather than C#?
which one do you see as the better language to begin with? (C++ is notably more difficult but is it worth it?)
>>52543484
>and you still have the advantage of proper memory management.
Haha, no.
