The Desktop team has just returned from our engineering sprint in Gothenburg, and as we begin the development cycle for Ubuntu 26.04 LTS, I’m excited to share what’s coming next for Ubuntu Desktop. Long-term support releases traditionally focus on stability, refinement, and a cohesive user experience across installation, daily use, security, and enterprise integration. Here is a look at the key themes and what we aim to deliver when 26.04 ships next April. Desktop Experience Gnome 50 and ne...
  • jlsalvador@lemmy.mlEnglish
    8·
    11 hours ago

    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?

    • ashx64@lemmy.worldOP
      3·
      7 hours ago

      All of those, apart from loop devices, are not technical limitations, but results from Canonical’s poor management and monopolistic desires.

    • caseyweederman@lemmy.ca
      1·
      7 hours ago

      Huh. I don’t know enough about Flatpak, I guess repo owners get to make that call? Do Flatpaks have a preinst equivalent? Could you theoretically have an empty Flatpak that installs snaps at a system level? I guess it would need explicit permission to write to the filesystem, which kinda seems to be the opposite of the purpose of Flatpak.
      And like, even if that is possible, the Flathub maintainers would probably reject it on principle. So I’m imagining CanHub with an extra step in the installation instructions that gets you to pipe a curl’d script into sh, at which point, what’s the point?