this post was submitted on 09 Mar 2024
544 points (95.9% liked)

memes

10443 readers
3617 users here now

Community rules

1. Be civilNo trolling, bigotry or other insulting / annoying behaviour

2. No politicsThis is non-politics community. For political memes please go to !politicalmemes@lemmy.world

3. No recent repostsCheck for reposts when posting a meme, you can only repost after 1 month

4. No botsNo bots without the express approval of the mods or the admins

5. No Spam/AdsNo advertisements or spam. This is an instance rule and the only way to live.

Sister communities

founded 1 year ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[โ€“] sloppy_diffuser@sh.itjust.works 5 points 8 months ago (1 children)

And not have to wait for a maintainer to update the package to have the latest version.

[โ€“] jj4211@lemmy.world 1 points 8 months ago* (last edited 8 months ago)

You think of distribution packaged rpms/deb, but the softwate developer can self publish, and you'll see plenty of self published packages in ppa, copr, flathub, and even just loose websites because it's not rocket science to make an apt or yum repository. However the distribution versions may take a little more time, but more likely to work together as a cooperative whole. Flathub has a decent shot by allowing concurrent versions of dependencies to install, while preserving the concept of updating dependencies independent of the package maintainers.

However, as you go down his chart, it's less likely that you'll reasonably update after install. You may get the latest at the second you install, but 6 months later you'll likely be stale. You may neglect to update npm in each and every project, or it may automatically dependency lock (because self publish nature results in developers having to vet dependency updates, and devs are lazy about that).