cmdchallenge VS prologue

~/git/cmdchallenge master ± inotifywait -m --event create,modify,delete . & [1] 110764 Setting up watches. Watches established. ~/git/cmdchallenge master ± git pull remote: Enumerating objects: 768, done. remote: Counting objects: 100% (209/209), done. remote: Compressing objects: 100% (24/24), done. remote: Total 768 (delta 200), reused 185 (delta 185), pack-reused 559 Receiving objects: 100% (768/768), 323.39 KiB | 16.17 MiB/s, done. Resolving deltas: 100% (474/474), completed with 10 local objects. From https://gitlab.com/jarv/cmdchallenge e97638c3..2c059b85 master -> origin/master * [new branch] next -> origin/next * [new branch] renovate/github.com-docker-docker-23.x -> origin/renovate/github.com-docker-docker-23.x * [new branch] renovate/github.com-mattn-go-sqlite3-2.x -> origin/renovate/github.com-mattn-go-sqlite3-2.x Updating e97638c3..2c059b85 ./ DELETE .asdf-plugins ./ CREATE .asdf-plugins ./ MODIFY .asdf-plugins ./ DELETE .envrc.example ./ CREATE .envrc.example ./ MODIFY .envrc.example ./ DELETE .gitignore ./ CREATE .gitignore ./ MODIFY .gitignore ./ DELETE .tool-versions ./ CREATE .tool-versions ./ MODIFY .tool-versions ./ DELETE Makefile ./ CREATE Makefile ./ MODIFY Makefile ./ DELETE README.md ./ CREATE README.md ./ MODIFY README.md ./ DELETE challenges.yaml ./ CREATE challenges.yaml ./ MODIFY challenges.yaml ./ MODIFY challenges.yaml ./ MODIFY challenges.yaml ...

I have written a bit of both, recently re-wrote a command runner for a side-project https://gitlab.com/jarv/cmdchallenge in Nim and found it very pleasant and much less verbose, which was a nice change from GoLang while keeping type safety. A good example is parsing JSON https://nim-by-example.github.io/json/ as you can do a lot with fewer lines of code. I think the main disadvantage of Nim is that there is less out there in the ecosystem, libraries, and it's more likely you will run into quirks and bugs in the standard library.

If you want to try an alternative to Jester, Prologue is very nice to use: https://github.com/planety/prologue

Well no language is perfect, but Nim can be used in almost every domain because of it's compilation targets(C, C++, JS) and it's fast compile times(who needs interpretation when compile times are that fast!):

* Shell scripting, I still assume most people will just use Bash tho: https://github.com/Vindaar/shell

* Frontend: https://github.com/karaxnim/karax or you could bind to an existing JS library.

* Backend: For something Flask-like: https://github.com/dom96/jester or something with more defaults https://github.com/planety/prologue

* Scientific computing: the wonderful SciNim https://github.com/SciNim

* Blockchain: Status has some of the biggest Nim codebases currently in production https://github.com/status-im?q=&type=&language=nim&sort=

* Gamedev: Also used in production: https://github.com/pragmagic/godot-nim and due to easy C and C++ interop, you get access to a lot of gamedev libraries!

* Embedded: this is a domain I know very little about but for example https://github.com/elcritch/nesper or https://github.com/PMunch/badger for fun Nim+embedded stuff!

Most of the disadvantages come from tooling and lack of $$$ support.

It doesn't https://github.com/planety/prologue/blob/devel/prologue.nimble

Jester is really great but I feel Prologue should get some attention too.

Nice! I want to also suggest the Prologue framework - here are the docs

Prologue is a great web framework in the Nim world. However, Prologue framework tries to avoid using macros. It is intended to reduce magic and reduce surprise. Macros could save you from redundant codebases. At the mean time, it could bring surprise. This article talks about how to extend the routing style outside Prologue without invading inside the web framework.

Prologue is a powerful and extensible web framework written in Nim language.