3 ms·

Golang didn't pioneer 'fat' binaries as the article claims. It may have made them popular again, but we have had compiled, self-contained, dependency-free execu

Golang didn't pioneer 'fat' binaries as the article claims. It may have made them popular again, but we have had compiled, self-contained, dependency-free executables for decades. If people are not aware of that, perhaps it's because scripting languages (or languages that use a VM) have come to so thoroughly dominate programming language discussions?

pjmlp 9y ago
I guess so. Usually everone that somehow thinks Go compilation model is inovative, never has used anything beyond scripting languages and possibily C in addition to them. MS-DOS used to call them "XCopy installs", NeXTSTEP had its fat binaries with directory structure, Windows and MacOS(pre OS X) can store all dependencies inside the .exe file and so on. In any case, fat binaries don't cover the dependencies with file system, other running servers or sandboxing.
- colejohnson66 9y ago
  > MacOS(pre OS X) can store all dependencies inside the .exe file and so on. On macOS / OS X, it’s actually a .app folder
  - pjmlp 9y ago
    Yes, but on Mac OS pre-OS X you could use resource forks for that.