News for hackers. Stuff that matters.
Re:C++ vs. Rust Build Times by jupp0r on Friday January 06, 2023 @02:14AM (#34271854)
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.
Re:C++ vs. Rust Build Times by pjmlp on Friday January 06, 2023 @02:34AM (#34271965)
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.

Re:C++ vs. Rust Build Times by bombolo on Friday January 06, 2023 @04:32AM (#34272755)
Because google decided we all want one big binary that contains the go runtime and weights at least 100MB
Re:C++ vs. Rust Build Times by mwcampbell on Friday January 06, 2023 @04:51AM (#34272875)
I have several Go-based binaries in my $HOME/bin, and not a single one is 100 MB.
Re:C++ vs. Rust Build Times by vegerot on Friday January 06, 2023 @05:25AM (#34273093)
And all of them combined compile faster than either of these implementations!
Re:C++ vs. Rust Build Times by bombolo on Friday January 06, 2023 @12:21PM (#34277702)
I'm honestly impressed, all my ones are at least 60MB
Re:C++ vs. Rust Build Times by vegerot on Friday January 06, 2023 @12:53PM (#34278271)
#itdepends on the kind of software you’re making
Re:C++ vs. Rust Build Times by jupp0r on Friday January 06, 2023 @07:31PM (#34283487)
Because we don't want to release software for each Linux distribution and deal with perpetually outdated libraries.