Hacker News Reader

> Why don’t I ever hear about Nim anymore?

Nim has some serious technical debt, and it seems they don't have the manpower for it:

https://github.com/nim-lang/Nim/issues/14719

A language, its stdlib, and its package ecosystem all relate, but are also distinct. It's not hard to do your own TLS/SLS wrapper with whatever defaults you like. When I run `nimble search ssl`, it seems at least 4 people have done such.

This is just to pick on your example. There is surely much other technical debt in the compiler itself. The solution to low manpower, if you otherwise like Nim (or D), is to try to help the open source effort at whatever level you can: do your own packages, tutorials/documentation, etc.

> Side Note: Why don’t I ever hear about Nim anymore??? It’s version 1.68 (and presumably stable), has very approachable syntax, claims great performance, provides a package manager, and allows the GC to be turned off (much like Dlang). What gives?

I don't know if it's still the case. But there were issues with Nim executables being incorrectly flagged as viruses in Windows. ^1

1.https://github.com/nim-lang/Nim/issues/17820

That happens to everything.

.NET (on Windows only), by having C++/CLI, which currently is up to date to C++17, plus language extensions for .NET environment.