That didn’t take long.
That didn’t take long.
I have a few cheap TLDs because as an individual I didn’t want to pay a lot of money for the dot com versions. But I’m not a company.
You’re right. There are multiple definitions of the word stable, and “unchanging” is a valid one of them.
It’s just that every where else I’ve seen it in computing, it refers to a build of something being not-crashy enough to actually ship. “Can’t be knocked over” sort of stability. And everyone I’ve ever talked to outside of Lemmy has assumed that was what “stable” meant to Debian. but it doesn’t. It just means “versions won’t change so you won’t have version compatibility issues, but you’ll also be left with several month to year old software that wasn’t even up to date when this version released, but at least you don’t have to think about the compatibility issues!”
Debian aims for rock solid stability
To be clear, Debian “stability” refers to “unchanging packages”, not “doesn’t crash.” Debian would rather ship a known bug for a year than update the package if it’s not explicitly a security bug (and then only certain packages).
So if you have a crash in Debian, you will always have that crash until the next version of debian a year or so from now. That’s not what I’d consider “stable” but rather “consistent”
I get conventional mail marked up like it is from the manufacturer claiming my warranty is expiring.
With the added fun bonus that all the things they claim to cover are engine related, and my car is an EV with no engine.