Re:On Go, Portability, and System Interfaces
by xyproto on Tuesday September 22, 2015 @06:13PM
(#10262075)
Not ideological reasons. The latest version of Go supports dynamic linking for some platforms.
Re:On Go, Portability, and System Interfaces
by pjmlp on Tuesday September 22, 2015 @06:18PM
(#10262099)
On Android there is no way around it, as native code can only be accessed via dynamic linking.
This is what some Go designers think of dynamic linking:
Re:On Go, Portability, and System Interfaces
by GauntletWizard on Tuesday September 22, 2015 @10:39PM
(#10263048)
And those reasons are clear and clear-cut. Dynamic linking is a net negative in most use cases, and certainly in all the use-cases that the Go developers are developing for, where reproducible builds are mandatory, code size is a tiny fraction of main memory, and code quality is very strictly maintained. When you've built a good development and deploy strategy, rebuilding and redistributing your binary is an everyday activity. There's no additional cost.
Re:On Go, Portability, and System Interfaces
by shadowmint on Tuesday September 22, 2015 @09:15PM
(#10262806)
Yeeesss... but ultimately, Go is also a pragmatic language.
Dynamic linking is coming to Go, like it or not; because it's a feature that is needed in certain circumstances, and that has been acknowledged, even by the Go team.
Re:On Go, Portability, and System Interfaces
by bahamat on Wednesday September 23, 2015 @01:04AM
(#10263404)
That same web page lists Linux as harmful.
Re:On Go, Portability, and System Interfaces
by marssaxman on Tuesday September 22, 2015 @06:22PM
(#10262109)
I'm happy to be an end user in a world where go components are becoming more common, because statically-linked executables are far less likely to break when I upgrade unrelated programs.
I'd really hate to be a distribution maintainer in a world where go components are common. Security bug in the TLS library? Time to download 14GB of updates!