News for hackers. Stuff that matters.
Re:Microsoft removes documentation for switching to a local ... by jjice on Tuesday June 25, 2024 @09:23AM (#40788313)
> There's some seriously dumb issues with it: Ubuntu snaps are terrible...

It's so upsetting that Ubuntu went so hard in on Snaps. I just end up with issues caused by their sandboxing with hardware and config access and you end up having to fight to find a normal .deb install for FF instead of that damn default Snap.

I hope the journey isn't too rough for you though - best of luck!

Re:Microsoft removes documentation for switching to a local ... by burning_hamster on Tuesday June 25, 2024 @09:56AM (#40788700)
I am also not a fan of the pivot to Snap. However, it is worth mentioning, that it has only been two years (I think, at least 22.04 LTS was the first release I had to wrestle with them on my machine), and the experience has become a lot better during this time.
Re:Microsoft removes documentation for switching to a local ... by bee_rider on Tuesday June 25, 2024 @11:07AM (#40789580)
It took them 7 years to figure out that nobody needed Unity. Hopefully Snap will get sorted faster.
Re:Microsoft removes documentation for switching to a local ... by G3rn0ti on Tuesday June 25, 2024 @09:50AM (#40788628)
I understand your frustration with snaps, but I consider it a very good distribution channel for commercial applications on Linux systems. Something that Appimage or Flatpak could not easily provide without a commercial entity backing it like Canonical.
Re:Microsoft removes documentation for switching to a local ... by vetinari on Tuesday June 25, 2024 @10:05AM (#40788811)
Snap is a dead-end; but as usual, it takes some time until Canonical realizes that.

If you want to easily distribute commercial applications, use flatpak. You could even have your own flatpak repo for your own products, if you wanted (it is really just static http).

Re:Microsoft removes documentation for switching to a local ... by tracker1 on Tuesday June 25, 2024 @10:36AM (#40789188)
Snap apparently has a few advantages, like supporting non-gui apps (for servers) which isn't a good fit for AppImage or Flatpak. That said, I generally stick to Docker for server apps.

I agree that the flatpak/appimage/snap options for apps, and in particular commercial apps is a decent idea. I think integration and permissions should probably move to something similar to the UX for phone apps though... it feels weird having to try to configure permissions that should be in the box.