4 ms·

Chrome is doing the exact same thing for the same reason. Dev builds are dynamically linked while release builds are statically linked. Works quite well, it's a

by jupp0r 4y ago

Chrome is doing the exact same thing for the same reason. Dev builds are dynamically linked while release builds are statically linked. Works quite well, it's a great technique.

pjmlp 4y ago
It is quite common in Windows, either produce lib or dlls for each set of main modules. In the old days it used to be quite common on UNIX world as well, no idea why "modern" Linux seems to have forgotten about this approach and always builds everything as a single project unit.
- bombolo 4y ago
  Because google decided we all want one big binary that contains the go runtime and weights at least 100MB
  - mwcampbell 4y ago
    I have several Go-based binaries in my $HOME/bin, and not a single one is 100 MB.
    - vegerot 4y ago
      And all of them combined compile faster than either of these implementations!
    - bombolo 4y ago
      I'm honestly impressed, all my ones are at least 60MB
      - vegerot 4y ago
        #itdepends on the kind of software you’re making
- jupp0r 4y ago
  Because we don't want to release software for each Linux distribution and deal with perpetually outdated libraries.