[dastbe]

i’ve made this argument before, but you can run a 1k engineering company in a monorepo with the tools and services that exist today. between improvements to bazel (and alternatives) and adjacent tooling like build caching/target diffs, core git scalability, merge queues, and other services you can just plug things together over a few days/as needed and it will just work.

all of the stuff that you can’t do easily yet (vfs for repo, remote builds) just isn’t relevant enough at this scale.

[spion]

Using bazel is nontrivial amount of effort (most of the open-source rules don't really work in a standard way due to the fact that google doesn't work in a standard way).

I guess with a 1K engineering company you can afford a substantial build team.

[dastbe]

this is actually quite a lot better these days as the tooling adapts to integrate. go has always been the gold standard, but java/kotlin works very well and js/ts are much improved by rules_js.

[popfs]

That looked like one large run-on sentence.