Mac OS: Cat, Dog, Cow, Panther, Some California park, your uncles house
deleted by creator
Bro thinks he is Nickelodeon 😭
Of all the things wrong with GNOME, their choice of logo is at the bottom of the list.
Their insistence that it be pronounced ‘guh-nome’ is a worse crime.
GNU as the animal or the initials, okay, sure. Debatable. Gnome is a whole-ass word. That is ridiculous.
Up there with QT insisting their name isn’t Q-T. The initials are a word. If you wanted it pronounced Qute you should’ve called it that.
As I tell my wife, feet are gross.
Your poor wife.
I’ll likely call it 6.0 since I’m starting to worry about getting confused by big numbers again.
I was looking a Linus/Linux comment, I was trying to remember at what point Linus said “I’m incrementing the major version because these numbers are getting too big, there is no major advancement”.
ill be downloading this image thank you very much
And there is OpenSUSE: 10 11 12 13 42 15
If 42 is a true to Sir Terry Pratchett, then I see anothing wrong with this.
It’s like that because KDE is based on Qt. On 🪟, It’s because they don’t care, and on GNOME, it’s for aesthetic reasons.
Can you explain the aesthetic reasoning for GNOME?
Simple, OP and some people just don’t know what they are talking about. There was no “aesthetic reason”.
One of the big changes in GNOME 40 (that would be 3.40) was the introduction of GTK4. People used to assume that the gnome major versioning scheme was tied to GTK, so loads of people were asking the devs when GNOME 4 was coming out.
To demistify this idea of one being tied to the other they just dropped the “3.”, specially since that part wasn’t that relevant and started with the 40.
women and gay men crave the big numbers
Gnome 40/41/etc is still 3.40/3.41/etc if I remember correctly
no they just decided to make 4.0 into 40
Everything should be date-based name releases.
If it’s released April, 2023 it should be 23.04 or similar.
Other schemes are arbitrary.
Change my mind.
How would you differentiate between versions with major api breaks?
Shhh, they don’t know what that means, let them live in bliss
Lol. Developers just need to know what date the api changed. Viola.
Gotta know, are you serious or joking here? Follow up question: are you a developer and have you ever worked on a medium+ sized project? The amount of dependencies you end up with is astounding, you can’t just “know” when all those APIs changed, that would be a full time job just to stay on top of. And that’s not even taking into consideration transitive dependencies. If a library doesn’t use semantic versioning, 99% of the time it’s correct to avoid it just to save yourself the headache.
Semantic versioning. If I have 1.0.0 and you release 1.1.0 I can be pretty confident it’s safe to update. If you release 2.0.0 I need to read the release notes and see what broke.
If I have version July2023 and you release August2023 I have no information about if it’s safe to update. That’s terrible. That’s really bad.
This is for dependency management and maybe apis more than OSs, but in general semantic versioning is a very good system. It should be used often.
