Linux
Welcome to c/linux!
Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!
Rules:
-
Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.
-
Be respectful: Treat fellow community members with respect and courtesy.
-
Quality over quantity: Share informative and thought-provoking content.
-
No spam or self-promotion: Avoid excessive self-promotion or spamming.
-
No NSFW adult content
-
Follow general lemmy guidelines.
view the rest of the comments
Hear me out: It still makes sense for servers, shared hosting, etc. So .... where Linux has predominantly been the tool of choice.
It probably does. And in e.g. such a headless system, it makes sense as the default. Or more likely, whoever set that system up set it up in the way they want it to behave, hand-editing config files be damned because that certainly wouldn't have been the only config file they had to edit.
From a home desktop computer perspective, however, it's baffling. At minimum that should be one of the questions in the graphical installer: "Would you like Debian to make your routine installation of software updates annoying? Yes/no. You cannot change your choice on this later without doing a bunch of scary commandline shit."
Oh I realize I didn't mention this in my original comment at all. I agree with you 103%. I want to write a separate comment about this very thing, updating things in general on Linux. I have my dad daily driving Linux along with me, and he's somewhere between a power user and a regular "need web, document editing and PDFs" type of guy, and there is such a wide spread of software from such a wide spread of "sanctioned" installation sources on Linux, that he never really knows how to update ... Anything.
Here's a random list of "ways to update a program" we have encountered in the last few weeks off the top of my head:
If anyone thinks of other ways to add to this list, feel free to post them, would give me a laugh for sure.
We are both definitely not going anywhere, but we have constant conversations about how it would be nearly impossible to daily drive Linux if you are not very technically inclined, and how these things make Linux very much "not ready for prime time", because people are simply used to "X needs update! Do you want to update now? [Yes] [No] [Later]", and the Update just ..... WORKING.
Couldn't you just replace the old appimage but have the same file name?
Also: If I (or my aforementioned dad) install an AppImage, that is named "Nextcloud-DesktopClient-4.0.4.AppImage" that sets up its own startup shortcut and so on, and then I download an update (because the program literally asked me to download the new AppImage), and the new file is named "Nextcloud-DesktopClient-4.0.5.AppImage", am I supposed to rename it to 4.0.4 manually? Rubs me the wrong way somehow. Or am I supposed to know to rename it to a version-agnostic filename before first opening it, so I don't break things when it updates weeks down the line? My dad wouldn't think of either of these options by the way.
You totally could, but like in my example in the parentheses, if stuff breaks, you have just killed your working version of a program, so I don't have the balls to do that.