You are viewing a single thread.
View all comments
-8 points

Unpopular opinion: snap is not so bad and genuinely useful for many things

I would rather have a snap than building from source or use some tar.gz archive with a sketchy install script

permalink
report
reply
27 points

Very unpopular

permalink
report
parent
reply
14 points

I would prefer manually writing each software using butterflies over having snapd installed on my system.

permalink
report
parent
reply
9 points
*

obligatory “there is always a relevant xkcd”

permalink
report
parent
reply
2 points

And what do they offer over flatpak?

permalink
report
parent
reply
3 points

Better cli experience and the permission prompts are two that come to mind.

permalink
report
parent
reply
5 points

A built-in way to have services running (which is why openprinting can make a snap of CUPS but AFAICT can’t make a Flatpak).

permalink
report
parent
reply
28 points
*

some tar.gz archive with a sketchy install script

I just can’t… like maybe I’m too old and that’s why I still can’t wrap my head around how we went from “./configure && make & make install scripts are almost the de facto way to install software in linux” to “a sketchy install script”. We’re living interesting times at Linux

permalink
report
parent
reply
10 points

Blame the thousands of supply chain attacks.

permalink
report
parent
reply
5 points

Last time I ran a corporate-made installer, it caused massive graphical glitches and lock-ups after waking from sleep. It basically gave my system computer-AIDS.

That’s why I never run scripts which are too long for me to easily understand outside a sandbox. Official distro repositories and Flatpaks are the only sources I have some level of trust in.

permalink
report
parent
reply
1 point

I remember those times too. The difference today is that there are so many more libraries and projects use those libraries a lot more often.

So using configure and make means that the user also has the responsibility of ensuring all those libraries are up to date. Which again if we’re talking about not using binary install, each also need a regular configure/make process too. It’s not that unusual for large packages to have dependencies on 100+ libraries. At which point building and maintaining the build for all of them yourself becomes untenable really. However I think gentoo exists to automate a lot of this while still building from source.

I understand why binaries with references to other binary packages for prerequisites are used. I also understand where the limits of this are and why the AppImage/Flatpak/snaps exist. I just don’t particularly like the latter as a concept. But accept there’s times you might need them.

permalink
report
parent
reply
1 point

I’d rather be able to use my web browser uninterrupted without it being updated while using it and be forced to restart it.

permalink
report
parent
reply
2 points

The updates download in the background and will install when you exit the snapped app. If you really don’t want automatic updates, you can run snap refresh --hold to hold all automatic updates or add a snap name to hold updates for that snap.

permalink
report
parent
reply
2 points

Nope. There have been multiple times where I have my browser open, in the middle of something and when I go to open a new tab/window I get a blank screen telling me I need to restart FF to continue.

permalink
report
parent
reply
14 points

I would rather have a snap than building from source or use some tar.gz archive with a sketchy install script

I agree, but that sounds like false dichotomy to me because snap competes with flatpak.

permalink
report
parent
reply
1 point
Deleted by creator
permalink
report
parent
reply
1 point

There are plenty of use cases that snap provides that flatpak doesn’t - they only compete in a subset of snap’s functionality. For example, flatpak does not (and is not designed to) provide a way to use it to distribute kernels or system services.

permalink
report
parent
reply

linuxmemes

!linuxmemes@lemmy.world

Create post

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 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!

Community stats

  • 6.6K

    Monthly active users

  • 1K

    Posts

  • 20K

    Comments