Yup this too. We’re basically seeing a more standardized and healthy way of managing shared dependencies in Flatpak that doesn’t sacrifice the developer or end-user for sake of a few megabytes.
Flatpak is still not able to fully replace native apps in certain situations, sure, but that wont be the case forever. If Ubuntu believes they can replace debs with Snaps I believe someone can do the same for flatpaks given enough time.
Flatpak lets people host their own repositories, which is where I think we’ll see distros becoming distinct if they DO choose to diverge from Flathub’s selection, such as choosing to block non-free software. Over time, though, people generally all just add flathub if it isn’t already available.
And, again, if you need something more finegrained than flathub, there’s no reason why distro maintainers can’t move to a nix-based infrastructure-as-code and you’ll be free to host a repo with all of your distro’s software packaged as code.
The power maintainers want over users is simply too much effort to justify as more apps begin to complain about packaging issues downstream, and apps become more complex to build. Users will inevitably bypass them. Devs will inevitably become hostile to downstream repacking.
Cinnamon and XFCE are outliers in that they try to be super stable, “complete” desktops, compared to GNOME and KDE that try to be bleeding edge and packed with new and changing features.
Benefits to both, but I can respect why Cinnamon and XFCE have been slow to adopt Wayland (to a fault, many would argue)
Not sure if that’ll stay much longer, either. I’m using using dual graphics with nVidia and Wayland on KDE works just fine. The only annoyance is that KDE doesn’t have very good touchpad gestures by default, but you also can’t modify them. Boo!
We have the basics down. But hopefully desktop-class RISC-V will be within our reach in a few years!
Immutable root filesystem.
Less user error from borking the root fs. And also less apps relying on the root filesystem would be good. Likely something to be achieved with portals and other XDG work.
Wayland only for all modern desktops.
Wayland will soon have the ability for a lot of cool features that X11 doesn’t have, such as storing session data to disk and relaunching into new desktop environments without relogging. This’ll make hybrid graphics a lot easier to manage as changes to the active GPU can be done dynamically without logging out and back into your system.
Greater adoption of XDG portals and XDG standards.
Linux is obviously great in many ways because it lacks a single solution to a given problem, and that it’s just a kernel, so most of your end-user system is totally configurable while still being a Linux system. However, we have a lot of overlapping work that makes said end-user systems hard to manage when standards collide. Hopefully Wayland will encourage developers to work through XDG portals and other common standards to make Linux user AND developer-friendly.
Nvidia drivers
A contentious issue, but I think the future of Nvidia drivers will be open source. The proprietary drivers have been a blocker in many ways as they’re ‘good enough’ and better than Nouveau, so no one is going to bother backing the FOSS project when the prop. project is better. However, lots of very smart devs are working on bridging the gap and leverage the newly open-sourced portions of NV’s drivers, which will hopefully manifest as the end of AMD/NV driver quality discrepancies.
WINE support improved for general desktop apps
Every few years we get a new “Photoshop WORKING on LINUX???” tutorial that has some cryptic setup instructions or github repo that eventually falls to the wayside. WINE is getting a lot more support thanks to Valve and I imagine starting to take on Windows apps for first class support will be a gamechanger for the creative industries that rely on certain Windows-only apps!
Ending the distro-specific packing systems.
Yup, the best saved til last. My boldest claim is that Flatpak is going to kill off the necessity for RPMs, Debs, APKs, etc. for most end-users. The flatpak size disadvantage is negligible in the age of terabytes, but it allows devs to ensure a consistent build environment for their apps on all platforms (something that has caused a lot of flame wars between Fedora and app devs in the past).
For people who DO need apps from reproducible, stable-based pipelines (eg. docker, sysadmins, IT professionals) we’ll see Nix becoming dominant. In fact, it’s already beginning to eat into docker/container build systems thanks to its powerful reproducibility and infra-as-code paradigms. It’s having a real boost after a relatively quiet first decade of life, likely thanks to features like Flakes that can spin up developer environments in seconds.
With proton the benefit can be +/- by quite a large margin to the point where I wouldn’t rely on this data to say that Linux is faster by default. Though it’s promising that Linux CAN compete with windows in performance despite the added layer of abstraction necessary to run many titles.