The Future of Flatpak

> Wick started his talk by saying that it looks like everything is great with the Flatpak project, but if one looks deeper, ""you will notice that it's not being actively developed anymore"". There are people who maintain the code base and fix security issues, for example, but ""bigger changes are not really happening anymore"". He said that there are a bunch of merge requests for new features, but no one feels responsible for reviewing them, and that is kind of problematic.

I think Red Hat should really be stepping up more here, especially since with RHEL 10 they stopped maintaining a ton of desktop packages with the advice for users of those packages being "get the package from Flathub instead of from us" (see https://docs.redhat.com/en/documentation/red_hat_enterprise_... , search for Flathub). If that's Red Hat's attitude towards desktop software, they should be providing the resources to make Flatpak a viable alternative.

> A user's Linux distribution may still be providing an older version of Flatpak that does not have support for --device=input, or whatever new feature that a Flatpak developer may wish to use. Wick said there needs to be a way for applications to use the new permissions by default, but fall back to the older permission models if used on a system with an older version of Flatpak.

I'm glad he brought that up as a problem. I maintain a game on Flathub that has audio and controller support. Because of the limited permissions granularity, that means that the game is displayed as requiring arbitrary device access (--device=input is too new, so the Flathub maintainers don't allow it in packages yet) and being able to listen to your device's microphone (the audio permission doesn't allow only accessing speakers but not microphones). I hope that Flatpak adds backwards compatibility for permissions so newer Flatpak versions can start having more granular permissions.

Red Hat has since walked some of this back. Firefox and Thunderbird were supposed to go Flatpak only for RHEL 10, but they eventually shipped rpms for GA.

Seems there were a myriad of causes for this including lack of Native Messaging, no ability to deploy policies centrally, and broken integrations with various other parts of the desktop ecosystem.

They walked back Firefox and Thunderbird, but Evolution, LibreOffice, GIMP, Inkscape, and Totem have all been dropped. Red Hat no longer packages an office suite, a raster image editor, a vector image editor, or a media player for RHEL. This means that even people using RHEL as a development workstation or something will have to download software from Flathub if they don't want to use a second computer for all their general office tasks.

Desktop is not a large market for Red Hat. Even their employees mostly use Fedora.

The only place I really see RHEL workstations is in special purpose applications, and in most of those the users either have a separate Windows box, or they Citrix/RDP into the corporate Windows environment to do normal office productivity things anyway.

About ten years ago I worked in a bioinformatics lab. All the work machines were centrally managed RHEL machines. I guess it's different now?

Ubuntu basically ate their lunch for the desktop case. It used to be that commercial software required SuSE or RedHat on the desktop to get support. But especially RedHat always suffered from the curse of being ancient compared to other desktop distros. When Ubuntu became big enough for commercial software to target, people chose that because Ubuntu was just more recent.

Also, several releases ago, RedHat already started to wind down their desktop efforts, just leaving server/container/cloud as the primary use case for RHEL, with desktops just as "this could also work". That latest decision to drop a lot of desktop related stuff is just a logical continuation of this policy.