> and save your users the headaches from needing to have a usable compile 
> environment.

That's way too negative, the binary will contain the required parts of the Nim 
compiler and its VM and all you need to do is to provide `lib/system/`, 
`system.nim` (and maybe strutils, etc) with your app and patch the line `let 
std = findNimStdLibCompileTime()` to something appropriate.

Nim doesn't have to be installed at all for this to work.

> (though IIRC there are limits by default that may surprise you and that can 
> be removed, e.g. how many iterations a single loop can have is limited to 
> 1,000,000 as this is meant to be used while compiling). Otherwise ...

That limit can be changed at compile-time but it's a very useful thing for 
sandboxing. In the few benchmarks that I did, the VM runs Nim code faster than 
Python's VM runs Python code. 

Reply via email to