News for hackers. Stuff that matters.
Re:Monorepos and Forced Migrations by skissane on Tuesday October 12, 2021 @09:37PM (#28847247)
> Rather than be able to pin something to a version that works, the culture is that first someone breaks you (or says, “this might break you, please figure out if it will and act accordingly”), then you have to dig around for the change that caused it, find the right person to approve a rollback, and then figure out how to prevent them from breaking you again

Shouldn't the person/team who makes a change take ownership of fixing any breakage it causes, rather than passing the buck to their customers?

It sounds like the real issue isn't anything as technical as monorepos-vs-polyrepos or software versioning policies, but rather a management and culture problem?

Re:Monorepos and Forced Migrations by cgrealy on Wednesday October 13, 2021 @04:49AM (#28849796)
> Shouldn't the person/team who makes a change take ownership of fixing any breakage it causes, rather than passing the buck to their customers?

That doesn’t feel scalable to me. I’d imagine some dependencies at Google run to hundreds of clients.

To take an OSS view, some packages run to hundreds of thousands. Imagine if the maintainers of react had to fix all their clients.

Re:Monorepos and Forced Migrations by ratorx on Wednesday October 13, 2021 @04:59AM (#28849857)
With React, it’s not possible because there’s no systematic way to change client code. With a monorepo, it’s more tractable.

It’s still not scalable in the sense that the downstream can make any change they want. They are restricted to changes they can either manually or automatically apply to client code in a reasonable amount of time. But that’s the trade off for being a heavily depended on library (which a lot of the time is an explicit decision).

Re:Monorepos and Forced Migrations by cgrealy on Wednesday October 13, 2021 @11:26PM (#28860213)
> With a monorepo, it’s more tractable.

Is it really though? Sure, it's technically possible, but it feels like a massive burden to place one on dependency.

Not only do you have to maintain your own lib, but you have to understand how every other project uses it.

Re:Monorepos and Forced Migrations by account42 on Wednesday October 13, 2021 @10:05AM (#28852215)
Sounds like a very good motivation to keep breaking changes to an absolute minimum.