7 ms·

Popup asking? Sounds exactly like what Flatpak/Portals are doing. Batteries included? That is the reason why X11 is/was shipped alongside Wayland for some

Popup asking? Sounds exactly like what Flatpak/Portals are doing. Batteries included? That is the reason why X11 is/was shipped alongside Wayland for some time. It will be dropped and XWayland remains for compatibility reasons. And Wayland has already some batteries X11 doesn’t, better scaling support. Security through Portals/Flatpak. We’re in 2023, screensharing works for some time now ;) We don’t get stuck in legacy hell like Windows. And we don’t cut off compatibility like Apple. Bumpy ride but prospects are good. Next thing? A new virtual console for userspace? Something like KMSCON? https://en.wikipedia.org/wiki/Kmscon https://en.wikipedia.org/wiki/Kmscon I don’t want delete the good old thing. I want see them alive and improving :). Without the usual “it must become worse before it becomes better”.

wing-_-nuts 3y ago
IIRC any time I've used a flatpak app, it's downloaded tons of dependencies along with it because everything is sandboxed. I know disk space is cheap but it's kind of silly to me that the flatpak version of an app is 500mb while the deb version is ~ 5mb.
- tristan957 3y ago
  That 500MB almost entirely the runtime, which is shared across apps.
  - ho_schi 3y ago
    Yep. It settles down as soon as you have more Flatpaks installed. But yes. Flatpaks require more memory and disk space and fixes in private libraries are not fixed by a friendly package maintainer for all packages. I use native packages from Arch for most stuff and for new hot or weird stuff Flatpak. Especially for Closed-Source weird stuff. I prefer most - if not all - handle by native packages because that is a core feature of Linux. But there will be always others for reasons. For example plugins, Vim relies here mostly on Vimplug. Steam is thing I need to accept but itself a candidate for Flatpak (currently I prefer the native package). And to be precisely, Meson is also a package-manager for C/C++ developers. PS: I also use Flatpaks when otherwise many unusual dependencies are involved. That one application using Qt? Flatpak. And vice versa some applications which doing well move from Flatpak to native package (Marker did that). PPS: GNOME-Software does a good job in handling native packages, Flatpak and LVFS at the same time. I use mostly pacman, flatpak and fwupd. But sometimes I need the captains approach “Linux. Make it so.”.
PrimeMcFly 3y ago
> We don’t get stuck in legacy hell like Windows. legacy hell hasn't been a thing for a long time, and flatpack basically uses the same solution Windows does - numerous redundant different versions of older libraries. > And we don’t cut off compatibility like Apple Without Flatpack or similar, Linux is honestly pretty terrible as far as backwards compatibility goes.

wing-_-nuts 3y ago

IIRC any time I've used a flatpak app, it's downloaded tons of dependencies along with it because everything is sandboxed. I know disk space is cheap but it's kind of silly to me that the flatpak version of an app is 500mb while the deb version is ~ 5mb.

tristan957 3y ago
That 500MB almost entirely the runtime, which is shared across apps.
- ho_schi 3y ago
  Yep. It settles down as soon as you have more Flatpaks installed. But yes. Flatpaks require more memory and disk space and fixes in private libraries are not fixed by a friendly package maintainer for all packages. I use native packages from Arch for most stuff and for new hot or weird stuff Flatpak. Especially for Closed-Source weird stuff. I prefer most - if not all - handle by native packages because that is a core feature of Linux. But there will be always others for reasons. For example plugins, Vim relies here mostly on Vimplug. Steam is thing I need to accept but itself a candidate for Flatpak (currently I prefer the native package). And to be precisely, Meson is also a package-manager for C/C++ developers. PS: I also use Flatpaks when otherwise many unusual dependencies are involved. That one application using Qt? Flatpak. And vice versa some applications which doing well move from Flatpak to native package (Marker did that). PPS: GNOME-Software does a good job in handling native packages, Flatpak and LVFS at the same time. I use mostly pacman, flatpak and fwupd. But sometimes I need the captains approach “Linux. Make it so.”.

PrimeMcFly 3y ago

> We don’t get stuck in legacy hell like Windows. legacy hell hasn't been a thing for a long time, and flatpack basically uses the same solution Windows does - numerous redundant different versions of older libraries. > And we don’t cut off compatibility like Apple Without Flatpack or similar, Linux is honestly pretty terrible as far as backwards compatibility goes.