On the other hand:

• Loop-device exhaustion (slow, though Ubuntu has increased the limit via a patch).
• A single point of failure due to Canonical’s repository imposition (a closed garden).
• Unmaintained branches and snapped apps.
• Implicit installation of snapped apps through the apt CLI instead of the originally supported packages 🤬 (what the hell, Canonical!? Are you doing the same crap as Microsoft?).

The server-side closed garden is the opposite of an open ecosystem and the open-source community. You can add custom repositories to APT or Flatpak. Every new snap interaction feels like another step toward forcing the user to use it, instead of offering cool features that convince users on their own merits.

The last change (installing snapped apps when you run apt install) was horrendous. What’s next? Installing snapped apps when the user runs flatpak install?

Good information here about EXO, and ChromeOS:

Neal Gompa (ニール・ゴンパ) 1 week ago

Is Exo going to continue to exist as a Wayland compositor? I figured it was going to be retired as ChromeOS turned into an Android overlay…

Fangzhou Ge 1 week ago

Yes, becoming Android overlay removes Chrome from the OS so Exo is going to retire. We still have to maintain Exo experience until the all ChromeOS device reach AUE or be updated to Android. Latest device AUE date I see are in 2033.

If folks don’t want Exo be listed we’ll just have Chromium here. Edited 1 week ago by Fangzhou Ge

Neal Gompa (ニール・ゴンパ) 1 week ago

I’m fine either way, if the Aura Shell is going to be around for a while, then it makes sense to include it.

I don’t even knowed that Chrome OS is/will be replaced by Android as an overlay.