Not saying this is not an issue (although it isn't really in most fields, except for things like embedded), but that the 656 KB for "Hello World" is because of the "upfront cost" in binary size.
I have spent sometime developing in Delphi years back, and this was even more true with it (simple hello world GUI app was over a megabyte [create new project and compile], complex GUI app was barely above it).
Language runtime.
http://blogs.msdn.com/b/abhinaba/archive/2008/09/15/how-many...
# echo 'main = putStrLn "hi"' > hi.hs
# ghc --make -optl=-static -optl=-pthread hi.hs -o hi
[1 of 1] Compiling Main ( hi.hs, hi.o )
Linking hi ...
# file hi
hi: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, not stripped
# du -hs hi
10.6M hi
# strip hi
# du -hs hi
4.4M hi
This is against musl libc by the way.In this case you would only pick .net if you were making something complex enough to warrant the size cost in exchange for the perceived benefits.
I mean comparing it to a raw native binary isn't an apples to apples comparison. What might be better would be comparing it to another VM based language like java / ruby / python / node. Where the size of the app is the scripts + the installed runtime.
Your one line "console.log('hello world!')" node app may be less than 1k but with the size of the node binary added in it becomes more comparable.