this post was submitted on 09 Mar 2024
545 points (96.0% liked)

memes

10324 readers
1696 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 [email protected]

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
[–] [email protected] 9 points 8 months ago (3 children)

Some of those can be good if you want a single command to install on any OS.

[–] [email protected] 5 points 8 months ago (1 children)

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

[–] [email protected] 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).

[–] [email protected] 3 points 8 months ago (2 children)

Bash/Sh on Windows? And what's so bad about 2-3 separate commands anyway?

[–] [email protected] 3 points 8 months ago* (last edited 8 months ago)

I assume he refers to npm/pip/cargo to be the multiple os option, not saying the last one is obviously better for multiple os. At least that has to be because that's the only option that is os independent.

Of course it sucks because the essentially uncurated dependency trees result in either instability on updates, or missing updates. Of course also the natural OS updater won't help you out with pip/cargo/npm, but it will help with apt, yum, snap, and flatpak.

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

I was talking about the other ones, but since you mention it, yeah, many people use Bash on Windows, from Git Bash which is part of Git on Windows, which pretty much any developer forced to use Windows will install in order to use Git.
Developers often prefer to have less interfaces to maintain when possible.

[–] [email protected] 1 points 8 months ago

Gets the job done, but shoudn't and isn't intended for non-programmer end user.
I'm not mad at small programs or developers with not much time to setup a distribution pipeline, they should be praised for their work at the program itself. But different OSes have different places to unpack a program and this allows simple updates, we should respect that for consistency at user end. Expect it's Windows, which is a unspecified mess anyway, let's go and unpack everything raw on C:\ or into user directory.