4 ms·
Except they don't entirely. As soon as the monorepo interfaces with the rest of the world (like with npm packages, let's say), the problem just gets shifted ont
by scotth 7y ago
Except they don't entirely. As soon as the monorepo interfaces with the rest of the world (like with npm packages, let's say), the problem just gets shifted onto the person trying to import/update a package. Which is further hindered by policy that discourages more than N versions of any given package.
Not that I'm against the policy or how it works. It just isn't "avoided" precisely.
- tosh 7y agoI wonder how Googlers decide what ends up in the monorepo and what is outside of it. Collaborative open source outside (e.g. Android, Fuchsia, Chrome, …)?
- scotth 7y agoIt's often the product team's decision. Anybody can spin up a Git repo when they need one. There's freedom there, but you miss out on a lot of tooling and healthy discipline by doing so. Once you're in the mono repo, you have to play by its rules (well...should anyway). Like in the case of npm packages I mentioned above.
- tosh 7y agoThanks for the context!
- umanwizard 7y agoPresumably google doesn’t use npm or other external package managers that download random things from the internet. Why would they?