3 ms·
You think about product lifecycles differently when you have a monorepo. Breaking change in a library? Just fix all the breaks in the same commit. Dependency he
by dehrmann 3y ago
You think about product lifecycles differently when you have a monorepo. Breaking change in a library? Just fix all the breaks in the same commit. Dependency hell? Not a problem when you have an ancient version forked in your monorepo. These are real problems customers face when they're not in your ecosystem, and Google doesn't always realize that. It was this same for App Engine. It wasn't a model 95% of customers wanted, but for Google spinning up services internally, it was great.
- influx 3y agoThat’s fair, I view Google as internally socialist, which I think works great until it hits a knee and doesn’t. My experience with Facebook was that Mercurial was awesome, but the multiple monorepos were unbearably slow.
- dehrmann 3y agoOne of the great ironies of capitalism is ~all companies are socialist internally, or at the very least command economies.