461
you are viewing a single comment's thread
view the rest of the comments
[-] Jumuta@sh.itjust.works 10 points 1 year ago* (last edited 1 year ago)

why? Do you mean "like" as in you'd rather have them than not, or that you think they're a good way to package apps?

[-] avidamoeba@lemmy.ca 6 points 1 year ago* (last edited 1 year ago)

I think they're a good way to package apps. Superior to Flatpak for sure. I like Flatpak too and if Canonical abandoned Snap tomorrow, I'd switch my snap-packaged apps to Flatpak. The only non-bullshit downside of Snap is the proprietary server-side and the lack of multi-repo support. I don't care much about either because I know implementing either is fairly uncomplicated and it will happen should the reason arise. If Debian wanted to start using Snap, it'd take them a month to get the basics working with their own server side. If the client side was proprietary too, I'd have had a completely opposite opinion on Snap. Finally Canonical supplies all the software on my OS. I use third party repos only when absolutely necessary. If Canonical ran a proprietary apt server side, I wouldn't even know, apt doesn't care. Some of the myriad HTTP mirrors could easily be running on IIS, or S3, or Nexus. The trust equation for snap is equivalent.

[-] NateNate60@lemmy.world 8 points 1 year ago

Oh boy, what a brave opinion to post. I respect that. I'm curious though, on your reasons for why you believe Snap to be superior to Flatpak.

[-] avidamoeba@lemmy.ca 3 points 1 year ago* (last edited 1 year ago)

Because you can package and deploy OS components with it. As a result you can build an OS with it, do foolproof updates of it and ...gulp, happy tear... rollback components without involving any other system like a special filesystem.

My bravery comes from being a software guy that's been doing OS software development for over a decade so I believe my opinion is somewhat informed. 😂 I'm currently working on a software updates implementation for an automotive OS.

[-] NateNate60@lemmy.world 6 points 1 year ago

I think this is just a difference in the use case. Flatpaks are designed for desktop applications while Snap was initially designed for exactly the purpose you describe.

[-] avidamoeba@lemmy.ca 7 points 1 year ago* (last edited 1 year ago)

The initial use case for Snap, when it used to be called Click (circa 2012-13), was mobile apps for Ubuntu Touch. Those were the same as desktop Qt apps, just using the a mobile theme and layout. Canonical developers just had the foresight to create a design that isn't limited to that use case. As a result Snap is a superset of Flatpak in terms of use cases. Flatpak can probably be rearchitected to match that if anyone cared. If that were the case I'd also be drumming it up.

The funny thing is, we wouldn't be having any of these discussions over the merits of Snap if RedHat came up with it instead of Canonical and the server side was OSS from the get go. When RedHat was cool that is. In fact likely Canonical would have been using thet too. Just like they use PulseAudio, Systemd, and Wayland.

[-] grue@lemmy.world 4 points 1 year ago

The only non-bullshit downside of Snap is the proprietary server-side and the lack of multi-repo support.

I think most people agree on that point, but believe that it's a big enough one to be a deal-breaker.

In what way is Snap superior enough to Flatpak to outweigh that downside?

[-] avidamoeba@lemmy.ca 3 points 1 year ago* (last edited 1 year ago)

Answered under the sibling comment: https://lemmy.ca/comment/4954544

[-] corsicanguppy@lemmy.ca 0 points 1 year ago

I think they're a good way to package apps.

Tell us you don't know why you need Single Source of Truth on package installation and content without using the phrase "dependency hell is self-inflicted".

[-] avidamoeba@lemmy.ca 1 points 1 year ago* (last edited 1 year ago)

A single source of truth for software is one way to solve that. There are others with different pros and cons in active use that have shown pretty good results.

this post was submitted on 17 Nov 2023
461 points (93.6% liked)

linuxmemes

21280 readers
1201 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 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