Re:Why are my Go executable files so large?
by nine_k on Sunday December 29, 2019 @04:30PM
(#21908634)
Google's anointed production languages used to be five: C++, Java, JavaScript, Python, and Go. Not much to reasonably standardize across, especially if a standardized solution ends up with more compromises than a custom one.
Re:Why are my Go executable files so large?
by pcwalton on Sunday December 29, 2019 @05:16PM
(#21908961)
But DWARF uses less space than Go's native format. So inventing a custom "linetab" format seems like the compromise, not using DWARF.
Re:Why are my Go executable files so large?
by nine_k on Sunday December 29, 2019 @08:25PM
(#21909977)
I suspect that the format is again copy-pasted from somewhere in Plan9, and existing Plan9 tools for it are ported, too.
Re:Why are my Go executable files so large?
by tyri_kai_psomi on Sunday December 29, 2019 @06:13PM
(#21909306)
Insert standardization XKCD. It's been tried. And even so, you can still use the "standard" coredump tool to analyze a Go program's coredump with decent success.
But wouldn't it still be nice to have a standardized way to analyze post-mortem dumps across languages?