this post was submitted on 16 Sep 2024
777 points (98.3% liked)
linuxmemes
21410 readers
837 users here now
Hint: :q!
Sister communities:
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
sudo
in 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!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't fork-bomb your computer.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Mad respect. I wouldn't have had that amount of time or patience due to personal circumstances, nor the ideological drive to see it work well, but it is people like you that compensate for those of us that can't or don't want to contribute to that same extent. All other preferences aside, I appreciate that contribution to a better ecosystem.
You're right, that would have been the worst "solution" - none at all.
Between my experiences with supporting users and corporate lingo, I don't think so. Provide a concise, maybe slightly propagandised ad about how snap is better and more secure, then provide the users with a highlighted button "Yes, I want to continue automatic security updates" and a subdued "No, I want to maintain it myself" along with a help pop-up for a slightly more technical "What's the difference".
Most casual users I know that just want things to work - myself included, in some cases - will just skim it, see the appealing buzzwords, click "Yeah whatever, I don't care". The more technical ones would probably google it, read the ensuing arguments and recommendations, and either decide like you did to give it a shot or end up responsible for their own thing (which is both the liberty and the jeopardy of Linux in general: you can do your own thing, but if it breaks, that's on you).
I wasn't aware of that detail (given I never cared about snap anyway, I never would have run into the issue). Paired with the unwillingness to remedy resulting problems, that is indeed a shitty move. I'd consider it on par with suddenly replacing my firefox with a version that worked very poorly*, which also caused me confusion and frustration, but unlike the firefox case, I don't see any graceful way of handling that transition in a user friendly manner.
*It just occurred to me that some of the issues may have been exacerbated by running on an HDD as opposed to an SSD. Prior to tossing Windows entirely, my SSD held my Win7 installation, while Ubuntu got its own partition on the HDD. I never migrated it to the SSD, instead using its limited 256GB to hold whatever games I was playing at the time.
Those are all good points.
Being hardliners about their philosophy is a common phenomenon in the Linux sphere. While I agree that it's not particularly user-friendly (and generally value open debate), I also feel that a distributor is within their rights to do what they feel is right rather than caving to users. Conversely, that's a philosophy I wouldn't want to endorse either.
The charge of paternalism is one I would level at Canonical too, given the concerns I expressed about pushing towards a monolithic, corporate controlled system. Good intentions notwithstanding, I worry it may pave the path to hell. They're more subtle about it, but that's no more of a redeeming quality to me than MS slowly creeping in new bullshit. (I'd gladly be wrong about that, of course - even if I may not want to use it, options are a good thing.)
But misinformation is an problem and I concede that I may well have fallen prey to it myself. I did try to search for info about open source options like what you mention, but my results and interpretations may have been biased, and I didn't spend enough time for a comprehensive understanding. I could make excuses, but that won't change the fact of my error.
I didn't. Thank you for taking the time.
It can't have been more than a few years ago, given that the snap move happened with 22.04 which released about 2.5y ago and I encountered that error. But I was, for all intents and purposes, a noob, so I can't exclude the possibility of user error. I'll take your word that this no longer happens.
I've never tried either nix or immutable distros. The idea of an immutable base, vetted for compatibility issues between what you refer to as the "building blocks", seems appealing from a "I don't want to worry about the details" perspective for casual use.
Android is convenient for another reason where I'm not sure how relevant it is to our context. It offers a unified version with a common set of features and interfaces, allowing app development relying on that version.
Exchangeable blocks can introduce complication in the same way that, for an example I'm familiar with, node package dependencies will feature a whole set of "at least this version" or occasionally "exactly this (major) version" specifications to ensure the individual parts all meet the requirements.
It's a tradeoff between modularity and reliability, as I see it, and both have their merits. I do tend to favour modularity, which is why I do appreciate the concept of snap as I have now come to understand it. Like I said, my misgivings are with Canonical more than the technology itself.
Likewise. I'm no fan of the adversarial nature of many conversations in the tech sphere either. Progress thrives on creativity, if tempered by skepticism and scrutiny. If we're willing to share perspectives, we can catch each other's blind spots. And if it comes down to personal opinions in the end, at least we can form those consciously and part ways a little wiser than before.
I'd be curious to hear about your other misgivings some time, but this conversation has been going on a while now and I may not have much time to read or respond the next few days. In any event, thanks for taking the time!