←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.207s | source
Show context
yurodivuie ◴[06 Apr 23 22:45 UTC] No.35475542[source]▶
Do smaller companies (smaller than Meta and Google) use these kinds of build tools much? It seems like a system that rebuilds everything whenever a dependency changes is more suited an environment that has very few, if any, external dependencies.

Is anyone using Buck/Bazel and also using frameworks like Spring, or React, for example?

replies(5): >>35475662 #>>35475737 #>>35475751 #>>35476098 #>>35478326 #
1. surrealize ◴[06 Apr 23 23:07 UTC] No.35475751[source]▶
I worked at a company that was about 150 people when I joined. It's not primarily a software company but the early team had a bunch of ex-google folks, and they chose Bazel. I encountered it for the first time there. We did use React, yes.

I really liked the cross-language aspect of Bazel. Having one command that could compile everything and produce a deployable container in a highly reproducible way is great. It really cut down on "what's your compiler/tool version etc."-type back-and-forth during debugging with other engineers.

The bazel JS/TS rules were tough to work with when we first started using it for JS (2018 I think), especially since we were using create-react-app at the time, and that didn't mesh well with the way bazel wants to work. It's gotten a lot better though.

If I was making the choice from scratch in a new company/codebase, I think it'd really depend on the team. You kind of need broad-based buy-in to get the full benefits IMO.