3 ms·

I think this will miss the point though. You can consider the specific .NET runtime as its own compute platform / operating system, regardless of what has to be

I think this will miss the point though. You can consider the specific .NET runtime as its own compute platform / operating system, regardless of what has to be installed on the machine for the program to actually run, and explore the limits of it. It will teach you a great deal about the binary format of the programs. You can do this for any format that stores executables, for any programming framework. .jar might be interesting, .py obviously isn't. You can do this for obscure old formats, or for something very common like the standard Linux .elf.

tempodox 3y ago
I disagree. I cross-compile F# sources with .NET on my Mac to get a stand-alone Linux executable without additional dependencies that I can upload to my server host. It's enough that I maintain the .NET stuff on my development host, I've got no desire to duplicate that work on the public host.
- H8crilA 3y ago
  What do you disagree with?
  - tempodox 3y ago
    Considering the runtime as something separate from a single program. I want both in the same binary.
    - H8crilA 3y ago
      It's not about considering this or that, but about making a fun little exercise that tells you how the binary format works.
BiteCode_dev 3y ago
> .py obviously isn't Although .zipapp is to Python what .jar is to .py. Probably even closer to .war. But for purely stand alone stuff, "nuitka3 /tmp/hello.py --standalone" does output a executable that can be used without the user to manually bring in the Python run time. In that case, the hello world is about 16Mb on Ubuntu. It would be interesting to do this with MicroPython though.