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.
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… rollbackcomponents 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.
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”.
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.
why? Do you mean “like” as in you’d rather have them then not, or that you think they’re a good way to package apps?
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.
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.
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.
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?
https://lemmy.ca/comment/4954544
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”.
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.