[esc_colon_q]

> But as the C++ community dreams of better tools, and dependency managers, maybe it would help to define the fundamentals more accurately: Our programs are a set of definitions, some of which are provided and maintained out-of-tree by other people. I think the more closely our tools adhere to that model, the better off we will fare in the long run.

> So maybe we need to ask fundamental questions about the compilation model and examine some beliefs we hold (For example “Compilers and build system need to be kept separated”. Do they? To what extent?).

I think you just put your finger on why Google is a monorepo - Blaze/Bazel kinda suck horribly (they feel super dated and could have been made much friendlier if they'd been designed from the ground up knowing what the pain points are, and esp if they weren't basically an ad-hoc set of new languages/syntaxes), but they're also awesome. The huge benefit is that you can make tools that work across everything and track monstrous dependency graphs.

[vlovich123]

I'm curious about this. I haven't felt that way about Blaze. What parts could be made friendlier?