←back to thread

Buck2: Our open source build system

(engineering.fb.com)
392 points mfiguiere | 3 comments | 06 Apr 23 16:05 UTC | HN request time: 0.636s | source
Show context
jeffbee ◴[06 Apr 23 16:57 UTC] No.35471168[source]▶
Hrmm, it makes performance claims with regard to Buck1 but not to Bazel, the obvious alternative. Hardly anyone uses Buck1 so you'd think it would be relevant.
replies(4): >>35471239 #>>35471275 #>>35472290 #>>35475655 #
1. kajecounterhack ◴[06 Apr 23 17:05 UTC] No.35471275[source]▶
I wonder if it's just because they don't have the same scale of data, since FB as a company uses Buck1/Buck2 but not Bazel?

They've clearly learned from Bazel though! I like the idea of not needing Java to build my software, and Starlark is battle tested / might make transitioning off Bazel easier.

replies(1): >>35472286 #
2. rajman187 ◴[06 Apr 23 18:20 UTC] No.35472286[source]▶
The author of Bazel came over to FB and wrote Buck from memory. In Google it’s called Blaze. Buck2 is a rewrite in rust and gets rid of the JVM dependence, so it builds projects faster but it’s slow to build buck2 itself (Rust compilation)
replies(1): >>35474731 #
3. bhawks ◴[06 Apr 23 21:27 UTC] No.35474731[source]▶
I believe this is an over simplification. Engineers who had used Blaze at Google reimplemented it at Facebook based on what they knew of how it worked.

Even Facebook's Buck launch blog does not offer this story of Bucks lineage and although the author worked on the Closure compiler at Google that is not all of Blaze.

https://engineering.fb.com/2013/05/14/android/buck-how-we-bu...