• 0 Posts
  • 23 Comments
Joined 1 year ago
cake
Cake day: June 23rd, 2023

help-circle







  • BTW there was a nice idea behind the only close button in early GNOME 3. Apps were intended to save the state on exit, so one doesn’t need to minimize windows, they can close it and reopen at any time and see the exact content of a window. But GNOME completely has failed to deliver that idea.

    What makes things worse, there was no clear way to keep apps on the background when the main window is closed. It was seemed as antifeature. But that was a different world where weren’t so much of internet service applications running on the background 24h a day. Now there is a background portal but with quite minimal support in the DE.






  • Flatpak was started by RH employee but has been developed with significant community effort.

    Flatpak uses ostree, which was originally created in GNOME for GNOME OS. And GNOME has contributors not only from RH but form Endless, Collabora, Purism and others.

    Flatpak can work with OCI remotes, this is what RH more interested in. And Flathub uses only ostree. OCI remotes are used in Fedora Flatpaks repacked from fedora packages with the runtime based on fedora. But who use it anyway.

    Flathub itself is independent community effort. It uses org.freedesktop.Platform based runtimes which are not based on any distro.

    XDG Portals are shaped by Flathub maintainers and applications developers where RH also doesn’t play significant role.







  • To go x86_64-only was a mistake for Arch. Distros like Fedora or Debian, or openSUSE have universal building systems and infrastructure for building packages for different architectures. Arch just creates unnecessary fragmentation for the GNU/Linux landscape: software need to be packaged for the distro and for the same time PKGBUILDs cannot be reused in general for anything to go full Arch Linux. Not for other architectures, not for servers or LTS. Only for a x86_64 desktop niche. Arch Linux doesn’t scale.