I think you’re very confused about the purpose of a systems programming language.

Nah, parent commentator and me both think Nim could be really large. The definition of "systems programming language" is defined by arbitrary lines.

Web apps are applications and are the opposite of systems software. Systems software would be the web server itself, or something that runs beneath the application layer.

Yes definitions are sometimes nebulous but that doesn’t mean words should lose all meaning and we should stop trying. Systems programming is a useful label for the boot stack, kernel, protocol implementations etc. which support the application layer.

The "systems" label only means those languages can do a few more low-level things, nothing more. There's no reason not to use it for other things as well.

I know this is hammered to death on HN, but you could definitely argue memory safety is a reason not to use systems languages for anything else.

Granted though it means what you meant by "it". I read that as "a systems programming language", but if you specifically meant Nim then I think it can enable a GC.

Not at all, and I've actually _used_ Nim for a few years now.

If Nim does not get a general purpose, batteries included web framework it will never reach escape velocity and will be left in obscurity despite all of the incredibly difficult and marvelous work Araq and the team has done.

I want them to succeed. I love the language!

people just say it's a systems language, it doesnt have to be only this.

I wonder why people haven't implemented it yet. Seems like a good project for me.

Has anyone tried prologue? https://github.com/planety/prologue

Yup, but it's more similar to "express" in Node than to a full framework like Django. I have plans to build a library on top of prologue for the ORM and database interaction and other cool features of Django that prologue currently lacks.

There is this attempt at a batteries included web framework: https://github.com/jfilby/nexus