> 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.
Was not intending to be negative, and this comment was in the context of compiling down to native code; you are of course correct (and that was my first paragraph - use the nim vm), > 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. Indeed, that's very useful for sandboxing; I remember when Python tried to introduce sandboxing, by way of putting such limits, but it never converged - there were issues with loops, string multiplications, e.g. `` 10e10 * 'hello world' `` or `` range(10e10) `` would blow up memory; they were fixed as they were found, but their approach of rewriting bytecode was doomed to fail (and did). Implementing these restrictions within the VM is much more practical. And I've never had a chance to use Nim VM for anything speed related, but the python speed comparison is very good news.
