• 2 Posts
  • 89 Comments
Joined 2 years ago
cake
Cake day: December 9th, 2023

help-circle














  • I cannot think of a single time I have manually created a .desktop file rather than using a GUI in the decades I have used Linux, and it has been a long time since I have even needed to edit the Start Menu at all installing packages takes care of it for me. Furthermore, even if this is a “paper cuts”, I doubt that people spend a lot of their time adding Start Menu items; by contrast, in Windows I get to experience the paper cuts of advertisements every single time I want to launch a program, and if I mistype the name of the program and press enter, then every single time I get to experience another paper cuts of launching Edge (which is not my default browser) to do a search in Bing (which is not my default search engine) for my typo.

    Likewise, for the last few years that I have been using WiFi with Linux, I have never once had to go outside of the GUI to adjust the settings.

    I won’t say that Linux has no annoyances, but I find using it to be a significantly more pleasant experience than using Windows overall, and my wife has never had a problem with it either.

    I really do not think that these “paper cuts” are representative of peoples’ general experiences with Linux.



  • The problem of there being a separate runtime for each video driver version was explicitly discussed in the article:

    If you are part of the huge part of the population who happens to own a Nvidia GPU, it’s a whole other can of worms. There are Flatpak runtimes that target specific Nvidia driver versions, but they must be matched with a compatible version installed on the host system, and it is not always a process as smooth and painless as one would hope.

    An improvement idea that is floating around is to, basically, just take a step back and load the host drivers directly into the runtime, rather than shipping a specific version of the userspace drivers along with the application. Technically, it is possible: Valve’s Linux runtime is pretty similar to Flatpak architecturally, and they solved this problem from its inception by using a library called libcapsule to load the natively installed host drivers into the Steam Runtime. This is the reason why it’s significantly rarer that an old Steam game fails to launch on a new GPU, compared to the same scenario on Flatpak!