INim VS jester

- `nim secret`[0]: code is interpreted with Nim's vm, it is limited to compile-time (e.g. no C/C++).

- `nlvm r`[1]: nlvm backend supports JIT compilation and repl-like interface was added in latest release.

- `inim`[2]: supports all nim code, but it's not really a true repl. It adds code to a file and recompiles it (you can see the source file with `ctrl+x`). I'd recommend to use it with clang compiler, because it's a bit faster than gcc in my experience. It's the best option right now. And I use it almost daily.

First two options have rudimentary input system. But you can get command history and left-right navigation by wrapping them with rlwrap (should be preinstalled on most *nixes): `rlwrap nim secret`, `rlwrap nlvm r`.

There are plans to support incremental compilation for the next Nim release (it is currently broken). That would improve inim and other repls experience significantly.

[0]: https://nim-lang.org/docs/manual.html#restrictions-on-compil...

[1]: https://forum.nim-lang.org/t/10697

[2]: https://github.com/inim-repl/INim

How to run those benchmarks?

At that Nim release page:

https://nim-lang.org/blog/2021/10/19/version-160-released.ht...

Is link to this benchmark:

https://web-frameworks-benchmark.netlify.app/result

Where nim is 2nd with 200k req/s, but it is using httpbeast:

https://github.com/dom96/httpbeast

That says it would be more useful to use jester:

https://github.com/dom96/jester

Jester has 150k req/s.

But, when looking at these:

https://www.techempower.com/benchmarks/

dragon, actix etc has about 600k req/s .

Also redbean has about 600k req/s, when I tested:

https://redbean.dev/

I tested like this:

git clone https://github.com/wg/wrk.git

cd wrk

./wrk -H 'Accept-Encoding: gzip' -t 12 -c 120 http://127.0.0.1:8080/

When I tested https://caddyserver.com v2, it did show about 800k req/s.

It would be very helpful to know how those benchmarks are actually done, so that I could compare what is actually fastest in real world, and not just use some for benchmark tested winning non-realistic code.

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.

See https://github.com/dom96/jester/blob/master/tests/alltest.nim#L105 and for a simpler syntax you can use the same @ as with params in the URL, so just: