Re:Evaluating Bazel for building Firefox
by jstimpfle on Tuesday October 29, 2019 @08:11AM
(#21386223)
"Small relative difference" - Most programs, probably including Bazel, have <1MB worth of code. Some programs have additional media files, but not all of them. And even in 2019, small programs do make a difference in convenience. Sometimes when you download things, sometimes when you copy files around, sometimes when you search the files on your computer...
A factor of 20, or 130, makes a huge difference if you consider all programs installed on your computer.
[ Parent
| on HN ]
Re:Evaluating Bazel for building Firefox
by danpalmer on Tuesday October 29, 2019 @08:25AM
(#21386320)
Currently Bazel has 48MB of source code in the `src` directory, plus another 125MB of integrations. Some of this will be tests, some will be build config, but that's probably in the ballpark of 100MB of source code. Adding somewhere between 20-100% for reliable running of that in ~all circumstances feels like a pretty solid engineering decision to me?
Re:Evaluating Bazel for building Firefox
by jstimpfle on Tuesday October 29, 2019 @09:05AM
(#21386635)
I haven't looked at the project. In my experience, 100K lines of C source code roughly corresponds to 1MB of native code. That might not be representative, though. But maybe it's just that that the rest of this project has some more of these "20-100% expansion will be ok" decisions.
Re:Evaluating Bazel for building Firefox
by danpalmer on Tuesday October 29, 2019 @09:39AM
(#21386977)
I just took these sizes from the master branch when I wrote the above comment. While that may have been true at one point, or is for C code, I suspect that is no longer the case in general. Between data files, resources, modern compilers optimising for speed over size, and more, I'd expect this to be significantly higher now.