56
why is it like this?
(lemmy.world)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 21 Jul 2023
56 points (100.0% liked)
linuxmemes
21019 readers
384 users here now
Hint: :q!
Sister communities:
- LemmyMemes: Memes
- LemmyShitpost: Anything and everything goes.
- RISA: Star Trek memes and shitposts
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack members of the community for any reason.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry will not be tolerated.
- These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudoin Windows. - No porn. Even if you watch it on a Linux machine.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.
Please report posts and comments that break these rules!
founded 1 year ago
MODERATORS
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.
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.
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.