Auf YouTube findest du die angesagtesten Videos und Tracks. Außerdem kannst du eigene Inhalte hochladen und mit Freunden oder gleich der ganzen Welt teilen.
Even if you use Flatpak, you need XOrg / XWayland on the host system.
Fedora Kinoite/KDE and the KDE Plasma desktop on its own are especially annoying, as I have no idea how to turn off those legacy support services from constantly running, like XWaylandVideoBridge (never used) or XWayland entirely.
I think Windows is just too bloated to also use Containers. With WSL they found a good way and apps should totally run in containers, but this is simply not yet done.
VMs would suck for efficiency as they rely on CPU virtualization and GPU passthrough. The former will never give native performance
Not that hard to stop wayland or xorg at the launch of a given application and restart it at that application’s exit. Of course, I only did it on the Raspberry Pi because the hardware lagged horribly running such apps with a gui/compositer/desktop the app wasn’t using in the background, but it wasn’t hard for me to get working, and its exactly how we did things with DOS apps and even some Windows games back in the WFWG 3.11 days.
Basically, there’s no technical reason the host operating system should have to be providing say X, KDE, Plasma, Gnome, Gk, Wayland, whatever, to a flatpack app that needs those things. Yes, the result is a larger flatpack, but that’s why flatpack’s do dependency consolidation.
Unless … Unless, you just really want to to run your games windowed with smooth window-resizing, minimization, maximization, etc.
Even if you use Flatpak, you need XOrg / XWayland on the host system.
Fedora Kinoite/KDE and the KDE Plasma desktop on its own are especially annoying, as I have no idea how to turn off those legacy support services from constantly running, like XWaylandVideoBridge (never used) or XWayland entirely.
I think Windows is just too bloated to also use Containers. With WSL they found a good way and apps should totally run in containers, but this is simply not yet done.
VMs would suck for efficiency as they rely on CPU virtualization and GPU passthrough. The former will never give native performance
Wsl is just a vm
True, that is virtualization. Inside you can run containers. Ironically, “docker desktop” uses that
The point of flatpack is supposed to be that it takes care of ALL dependencies. So you’re saying it doesn’t deliver on that promise?
Not all dependencies. Flatpak is an application, and a display server is outside of an application.
Closing an app should not result in a black screen XD
Not that hard to stop wayland or xorg at the launch of a given application and restart it at that application’s exit. Of course, I only did it on the Raspberry Pi because the hardware lagged horribly running such apps with a gui/compositer/desktop the app wasn’t using in the background, but it wasn’t hard for me to get working, and its exactly how we did things with DOS apps and even some Windows games back in the WFWG 3.11 days.
Basically, there’s no technical reason the host operating system should have to be providing say X, KDE, Plasma, Gnome, Gk, Wayland, whatever, to a flatpack app that needs those things. Yes, the result is a larger flatpack, but that’s why flatpack’s do dependency consolidation.
Unless … Unless, you just really want to to run your games windowed with smooth window-resizing, minimization, maximization, etc.
Alt-tabbing to another application (e.g. web browser) should not force you to close the game
… and why would it? Again, I only set it up like so on the Raspberry Pi(2B iirc) due to hardware limitations.