I'm gaining some insight into semver (Symantec versioning, aka 1.0.0) for the open source project didi.land

While attempting to understand smaller details for once, I am of course actually thinking about what it means to release software, a question that oddly I have managed to avoid in my job for many years, but as we are in a dev-ops world, it's time to dig in and try to understand.

3 little numbers which we might already be aware of, major.minor.patch as defined by the specifications, this is not a post about that, the semver spec does an ... Okayish job of that, perhaps il do a semver for humans post sometime?

Back on tangent, what the heck is a backwards compatible change, why do I want to go backwards? Can somebody spell it out for me.

My previous understanding of semver was, major, it's a brand new product, don't expect a piece of code to work with 1.0.0 or 0.0.0 my PlayStation 8 won't run disks from PlayStation 9?

Semver starts talking about API's and that is the most broad term, as a web developer, an API is a public set of endpoints 🤦‍♂️, but I can expect that on occasion it refers to library code yes, I'm struggling to contextualize it. API might also mean npm, given I replace the word API with npm, it kind of makes more sense.