←back to thread

Buck2: Our open source build system

(engineering.fb.com)
392 points mfiguiere | 1 comments | 06 Apr 23 16:05 UTC | HN request time: 0.266s | source
Show context
phendrenad2 ◴[06 Apr 23 21:48 UTC] No.35474996[source]▶
> Build systems stand between a programmer and running their code, so anything we can do to make the experience quicker or more productive directly impacts how effective a developer can be.

How about doing away with the build system entirely? Build systems seem like something that shouldn't exist. When I create a new C# .NET app in Visual Studio 2019, what "build system" does it use? You might have an academic answer, but that's beside the point. It doesn't matter. It just builds. Optimizing a build system feels like a lack of vision, and getting stuck in a local maxima where you think you're being more productive, but you're not seeing the bigger picture of what could be possible.

replies(14): >>35475210 #>>35475243 #>>35475249 #>>35475260 #>>35475271 #>>35475272 #>>35475320 #>>35475645 #>>35476535 #>>35476550 #>>35477035 #>>35480031 #>>35485001 #>>35487462 #
stonemetal12 ◴[06 Apr 23 22:54 UTC] No.35475645[source]▶
I am not sure I understand your point. I click build in VS, whatever VS does it takes 2 minutes.

Supposedly the C# compiler can compile millions of lines per second, but my not millions of lines of code project takes a minute to compile so it must be wasting time doing something, and could use some optimization.

replies(1): >>35476226 #
1. phendrenad2 ◴[06 Apr 23 23:57 UTC] No.35476226[source]▶
Regrettably, your observation doesn't prove your point. It's common knowledge that Visual Studio is very slow. It's entirely unknown how much of that slowness is related to the build system (using that term in the same sense as buck2).