4 ms·
> Didn't someone on the team say "hey, it takes 10 seconds to run git status, can we move this junk out and do this another way??" Why do you assume they didn'
by arinlen 4y ago
> Didn't someone on the team say "hey, it takes 10 seconds to run git status, can we move this junk out and do this another way??"
Why do you assume they didn't?
Just because they arrived at a different conclusion than you that doesn't mean they didn't thought about it. I might very well mean you did not considered the tradeoffs they had to take into account, mainly because you're out of the loop.
- rtpg 4y agoOne reason for doing this is that someone might be using a very small set of the monorepo, so having everything prebuilt means that in general things are very fast, without constantly having to rebuild chunks of your system. This is, I think, very common with stuff like browsers, where you have artifact checkouts that basically include built stuff since otherwise you're sitting there compiling forever all the time. Stuff like Bazel in theory helps with this, but tools that help with this are either super idiosyncratic about how they work (meaning hard to adopt) or outright don't work. I mean personally I would find that pretty annoying and unclean but I like DAGs.
- whynaut 4y agoThey’re not assuming anything, but stating that the post itself does not cover this well/at all.
- heyparkerj 4y agoThe post itself covers in the intro that they made the conscious decision to go with a monorepo, accepting the downsides of it. Much more than this article though, I'd like to read one discussing that decision and why they went that direction.