I first started working on emoji-picker-element back in May, about three months ago. Now I run npm-check-updates, and there are 28 packages with updates, including 8 with breaking changes. One of the packages has had *four* major versions since I last checked.

I know I live and breathe in the Node community, but sometimes I have to wonder: what is up with the Node community?

I mean, here's the thing: updates are great. Release early and often (or whatever). What bothers me is the cadence of *breaking* changes, as these have a cost for consumers: I now have to go and check the CHANGELOG for each of those projects, read every major version release, and figure out if something is going to break. Or I can just open a PR and hope my tests would catch any failure.

At the very least, breaking changes should ideally be grouped together to minimize churn.

OTOH, open-source maintainers literally owe me nothing, and releasing frequent breaking changes maybe makes their lives easier. They can reduce baggage and iterate more quickly. So maybe I should just zip it and be happy that there's all this great free software out there?

Follow

@nolan I think that's the party line.

· · Web · 0 · 0 · 0
Sign in to participate in the conversation
Mastodon

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!