Re: Nim developer retention data and out-of-date packages
Nim isn't something you just quit. A part of Nim stays in you, always. Every missing semicolon that D smacks you for, every undefined WTFism in C++, every second you wait for your 40mb Golang binary to upload, every time you realize that half of your screen is taken up by repetitive boilerplate
Nim developer retention data and out-of-date packages
Some people are just waiting for v `1.0`