Nim 1.0
Congrats to the Nim team.<p>One thing that is frustrating for anyone hearing about Nim for the first time is that it&#x27;s really hard to look at what appears to be yet another slightly different take on Rust or Go and intuitively understand why it exists.<p>There is absolutely a grid that can be populated: who started this, is it corporately affiliated, what languages is it similar to, what is the motivation of its creators, what is the philosophy driving its design, is it intended to be an eventual competitor or replacement for languages XYZ, where does it sit on the spectrum between raw assembly and MS Access, is it intended to be a &quot;systems language&quot; eg can you write a kernel or device driver using it, does it require a VM, is there corporate support available, how established is the developer community, are there books and courses, does it have garbage collection, is it a compiled language, is it a strongly typed language, what are the three perfect use cases, how stable is the API, what&#x27;s the package management story, does it have a reasonable standard library, is there editor support for color coding and linting, what&#x27;s the job market look like, is the documentation well-written, and most importantly, if we all got in the same room, would I want to hang out with the people excited about this language?<p>The cost of learning yet another language vs actually spending your finite spare time building something (or with your loved ones, or reading, or sleeping, or making art) is insanely huge.