[throwup]

> it'll take time for the dust to settle. Just like Unity / Wayland

There's a particular irony to this statement. Before adopting Wayland, Canonical tried to do their own thing with Mir[1]. Years later they gave up and reluctantly adopted Wayland. Their investment in Snap rhymes with this. Snap is an inferior competitor to Flatpak, and in the end it's likely the dust will settle for Snap the same way it did for Mir—in the dirt.

Canoncial as an organization has some serious NIH syndrome and they are putting "Linux on the Desktop" through a lot of unnecessary pain.

[1]: https://en.wikipedia.org/wiki/Mir_(software)

[asdajksah2123]

I don't think Snap is an inferior solution, as much as Canonical is trying to put Snap where it doesn't belong.

AFAICT, Snap is a pretty good solution for server side apps. This is pure speculation (and I don't even know if the timelines line up), but I suspect Canonical developed Snap for server apps, but something made it economically non viable (maybe the popularity of Docker?) and so they now needed to generate money through it some other way and they decided to do it by using it as a workstation app distribution mechanism, and by locking it down for enterprise.

[Arnavion]

"Server apps" can just be systemd services with isolation configured to your liking. Even if it's necessary that the service include some arbitrary subset of userspace, that can still be done with systemd portable services.

[padraic7a]

Mír still exists. It's a Wayland compositor now for IoT but it's still there.

[Arnavion]

throwup is referring to Mir the display server that implemented Mir the display protocol, because Canonical didn't understand Wayland, didn't talk to anyone that did, and so decided they needed their own protocol.