Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Why is a speed part of the Go language contract but footprint of the executable is not? I, for one, would be quite miffed if an update of the Go compiler would mean an application would no longer fit on my mcu. That is worse then the application running slower.


> Why is a speed part of the Go language contract but footprint of the executable is not?

Because footprint of the executable has pretty literally never been, Go has always had deficient DCE and generated huge executables.


It also generates pretty slow executables. That doesn't invalidate the point.


Ideally it could be a compiler flag. Even more ideally, you could tell your compiler what the max size you want is and then it would optimize for the best speed at a given executable footprint.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: