3 ms·
Maybe I'm being too simplistic but this should be a characteristic of the implementation and not the language? Then again I don't know much about the technical
by psychphysic 4y ago
Maybe I'm being too simplistic but this should be a characteristic of the implementation and not the language?
Then again I don't know much about the technical details here (when do you or don't you need your own runtime). It seems baffling to me with all the cruft and bloat in a modern windows install do you still have to install so many microsoft runtimes.
- weavie 4y agoThe difficulty with a lot of dynamic languages is that it is very difficult to determine at compile time what parts of the runtime are not going to be invoked so you largely end up having to include the entire platform in the executable.
- crabbone 4y agoI really struggle to think about a language that doesn't usually need a runtime. Some can produce binaries that don't need a runtime, but usually you need to jump through hoops to make that happen. We just don't notice that typical C programs need libc and pthreads. Or that C++ programs on Windows require that cursed Microsoft Visual C++ Runime DLL which is always missing, but has few dozens of copies all over the system of the miserable Microsoft slave. Go doesn't produce fully statically linked binaries by default. I used to make "from scratch" Go containers and, in general case, you need libc in them, unless you are willing to go through pain of statically linking with it. Typical / practical Rust programs will also depend on libc and pthreads (but, sure, you can do w/o).