Why are my Go executable files so large?

Re:Why are my Go executable files so large? by Too on Monday December 30, 2019 @03:22AM (#21911681)

Java and .NET can also get backtrace at runtime. Can't remember if they are symbolized or not but i think they are. How do they handle this?

[ Parent | on HN ]

Re:Why are my Go executable files so large? by thu2111 on Monday December 30, 2019 @03:54AM (#21911869)

They generate unwind information on the fly as they compile the code which is then stashed to one side, compressed and accessed only if a true language-level stack trace is required. Also they don't expose argument or return values in stack traces.

[ Parent | on HN ]

Re:Why are my Go executable files so large? by ComputerGuru on Monday December 30, 2019 @03:42AM (#21911787)

They’re interpreted/JIT’d and not compiled like golang.

[ Parent | on HN ]

Re:Why are my Go executable files so large? by pjmlp on Monday December 30, 2019 @03:51AM (#21911836)

They, have release and debug build modes.

.NET has AOT support since ever via NGEN, followed by Mono AOT, Xamarin,IL2CPP, Bartok, .NET Native and a couple of less know projects.

On Java side AOT has been always supported by JVMs for embedded deployments like Aonix (now part of PTC, PTC, Aicas, ExcelsiorJET, IBM J9.

And nowadays there is SubstrateVM as well, renamed recently as Graal Native Image, part of OpenJDK since Java 11.

[ Parent | on HN ]

Re:Why are my Go executable files so large? by andor on Monday December 30, 2019 @08:02AM (#21913063)

Not entirely true with regards to the question.

Yes, Java is interpreted and JITed, but on the bytecode level. When compiling sources to bytecode, line number information is written to class files.

[ Parent | on HN ]