this post was submitted on 02 Oct 2023
813 points (95.6% liked)

linuxmemes

24305 readers
2112 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
  • Don't get baited into back-and-forth insults. We are not animals.
  • 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.
  • 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, no politics, no trolling or ragebaiting.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
  • 5. πŸ‡¬πŸ‡§ Language/язык/Sprache
  • This is primarily an English-speaking community. πŸ‡¬πŸ‡§πŸ‡¦πŸ‡ΊπŸ‡ΊπŸ‡Έ
  • Comments written in other languages are allowed.
  • The substance of a post should be comprehensible for people who only speak English.
  • Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
  • 6. (NEW!) Regarding public figuresWe all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations.
  • Keep discussions polite and free of disparagement.
  • We are never in possession of all of the facts. Defamatory comments will not be tolerated.
  • Discussions that get too heated will be locked and offending comments removed.
  • Β 

    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 remove France.

    founded 2 years ago
    MODERATORS
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] [email protected] 6 points 2 years ago (4 children)

    This computer idiot would also like to know why snap bad.

    [–] [email protected] 17 points 2 years ago (1 children)

    The main reason is that it is completely controlled by Canonical, with no way to add alternative repos.

    [–] [email protected] 2 points 2 years ago (1 children)

    It's worth noting you can bypass the repo, and install snaps that you downloaded from some other source - see https://askubuntu.com/questions/1266894/how-can-i-install-a-snap-package-from-a-local-file.

    That doesn't give you a separate "repo," but it does allow you to install snaps from anywhere.

    [–] [email protected] 6 points 2 years ago* (last edited 2 years ago) (2 children)

    You can, but that completely negates the reasons why you'd want to have a repo system in the first place. You gotta do the legwork to get updates, for example.

    [–] [email protected] 2 points 2 years ago

    And to be explicit about it, zypper, dnf, apt, flatpak all have a specific mechanism to declare repositories and one 'update' check will walk them all.

    snap does not, and manually doing a one off is useless. AppImage also has no 'update' concept, but it's a more limited use case in general, it's a worse habit than any repository based approach.

    [–] [email protected] 1 points 2 years ago

    This isn't necessarily true - a developer choosing to not include their app in a repo can always opt for a self-updating mechanism.

    Don't get me wrong - repos and tooling to manage all of your apps at once are preferred. But if a developer or user wants to avoid the Canonical controlled repo, I'm just pointing out there are technically ways to do that.

    If you'd question why someone would use snap at all at that point... that would be a good question. The point is just that they can, if they want to.

    [–] [email protected] 3 points 2 years ago

    I hate it for the refresh nag messages alone.

    The default Firefox in Ubuntu is a snap and I only knew that because due to nagging and having to restart constantly while I was using it and had to learn about snaps and how to install Firefox without them on Ubuntu.

    [–] [email protected] 2 points 2 years ago* (last edited 2 years ago)

    If something exists in native form, use that. If it doesn't or you want some sandboxing (and there is at least some argument for a containerized version that brings all its needed dependencies, for developers not having to test for every linux for example) there's flatpack or appimage. Snap is just Canonical's proprietary alternative to flatpack. And also worse in basically any aspect. So they shove it down their users throat instead. Even for stuff that would be available natively and should just be installed via the normal package manager. And to make really sure, nobody is avoiding their crap, they also redirect commands, so for example using apt to install your browser automatically redirects your command to snap install...