this post was submitted on 21 Jul 2023
15 points (100.0% liked)

linuxmemes

20762 readers
1803 users here now

I use Arch btw

Sister communities:

Community rules

  1. Follow the site-wide rules and code of conduct
  2. Be civil
  3. Post Linux-related content
  4. No recent reposts

Please report posts and comments that break these rules!

founded 1 year ago
MODERATORS
[email protected]
[email protected]
15
why is it like this? (lemmy.world)
submitted 1 year ago by [email protected] to c/[email protected]
11 comments fedilink hide all child comments
 
top 11 comments
sorted by: hot top controversial new old
[–] [email protected] 6 points 1 year ago

Honestly, I just wish they would ditch that disgusting foot logo. I hate it.

[–] [email protected] 3 points 1 year ago

Mac OS: Cat, Dog, Cow, Panther, Some California park, your uncles house

[–] [email protected] 2 points 1 year ago

[–] [email protected] 1 points 1 year ago

Even the old dog did it:

In 1999, Slackware saw its version jump from 4 to 7. Slackware version numbers were lagging behind other distributions, and this led many users to believe it was out of date even though the bundled software versions were similar. Volkerding made the decision to bump the version as a marketing effort to show that Slackware was as up-to-date as other Linux distributions, many of which had release numbers of 6 at the time. He chose 7, estimating that most other distributions would soon be at this release number.

[–] [email protected] 1 points 1 year ago

I'll likely call it 6.0 since I'm starting to worry about getting confused by big numbers again.

~ Linus Torvalds

[–] [email protected] -1 points 1 year ago* (last edited 1 year ago) (2 children)

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.

[–] [email protected] 4 points 1 year ago (1 children)

How would you differentiate between versions with major api breaks?

[–] [email protected] 3 points 1 year ago (1 children)

Shhh, they don't know what that means, let them live in bliss

[–] [email protected] 0 points 1 year ago (1 children)

Lol. Developers just need to know what date the api changed. Viola.

[–] [email protected] 1 points 1 year ago* (last edited 1 year ago)

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.

[–] [email protected] 2 points 1 year ago

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.