4 ms·
You do realize that golang statically compiled binaries contain the go runtime right? So, all the concerns that you mentioned are applicable to go as well, e.g.
by throwdbaaway 6y ago
You do realize that golang statically compiled binaries contain the go runtime right? So, all the concerns that you mentioned are applicable to go as well, e.g. a golang app may be buggy when built with version X, while another golang app may have GC issue when built with version Y, and yet another golang app would be vulnerable unless rebuilt with version Z. [1][2][3]
Don't drink the Kool-Aid, golang is just a more opinionated and much less capable cousin of Java/JVM. And for many companies, that could be the right trade-off.
[1] https://groups.google.com/forum/m/#!topic/golang-announce/mVeX35iXuSw https://groups.google.com/forum/m/#!topic/golang-announce/mV...
[2] https://groups.google.com/forum/m/#!topic/kubernetes-security-announce/PtsUCqFi4h4 https://groups.google.com/forum/m/#!topic/kubernetes-securit...
[3] https://groups.google.com/forum/m/#!topic/golang-announce/65QixT3tcmg https://groups.google.com/forum/m/#!topic/golang-announce/65...
- bsaul 6y agoexcept that the developer controls it, since its is embedded. As such it follows the exact same lifecycle as the code itself ( versionning, testing, etc).
- vips7L 6y agoThis is misinformed. jlink has existed since jdk 11 and allows the developer to produce a custom JVM to ship with their application. jpackage also now exists to create installers for whatever platform your on. It is you the developer who are responsible for packaging your application correctly.
- hkeide 6y agoWhy doesn't Kafka do this?