The flatpak size disadvantage is negligible in the age of terabytes
the issue is overstated as most flatpaks use the flatpak platform runtimes and share their own libraries in a similar manner to the host, yes its separate libraries, but its not dozens of disparate copies like some detractors of flatpak seem to state
Sorry I didn’t see a notification for this.
It’s a different work flow installing software. Flatpak first mentality, then install stuff in a Toolbox container, if that doesn’t work layer the rpm.
Being able to rebase has been helpful, I’ve based forward to rawhide a few times to try new packages and then rebase back to stable.
You lose things like being able to use packages out of copr, but used to only really use that to test new versions of KDE. However the devs created a branch for KDE testing anyway, so nothing lost.
Happy to answer any specific questions you might have
Don’t know if this counts - used Fedora KDE for about a decade and then last year moved to Fedora Kinoite. It’s essentially the same, but is OSTree based and immutable. I like the solid base, the rebasing function and containers
Pipewire has been great, except for some edge cases
Still got passthrough issues 2years later
It doesn’t even need to be a script you could just alias the 2 commands on a single line to a command in bashrc
People who hate them have never driven them
Move to silverblue/kinoite and when the urge to use another DE just rebase the OStree to the other branch - Silverblue for Gnome, Kinoite for KDE, Sericea for sway, Vauxite for xfce and there are some other not yet official branches for other DEs on Quay
You can get usb-c aux adapters that split off a charge port too, they aren’t very expensive either
I went back to a pixel, as I couldn’t get my oneplus with lineageOS to do Android pay, after custom roms on all my phones since the HTC Dream, I have been running stock for the last 18 months, kind of miss it
At 720p you can, not 1080p or 2160p - Linux meets minimal widevine
Things like androidpay/apple pay type functions require a chain of security checks, on Android it’s levels of safety net. some banking apps require similar
Before the rise of Android and ios I’d have said it was possible, but the goal posts have shifted pretty far. Unless something backed by a corporate entity or government rises Up, it’s a no. A chromeos type thing for smartphone is not going to happen for mass market, because there is already Android.
Discounting Android, the last mile of what a smartphone is capable of can not be accomplished in Foss manner, without end to end verified OS images and some kind of secure enclave for banking and “security” features, carriers and banks are not going to get on board any more. Convenience features like DRM video streaming, casting also probably are not achievable either
I pay $17AUD a month for a family plan
really? From the outside looking in, it looks like most Christians are atheists just putting on a show because it’s expected of them. Its the only logical explanation for otherwise rational people buying into that twaddle
The back fingerprint reader used to have gestures, so swiping down on it could for example open the notification shade. Was really good for not having greasy fingerprints on your screen
that’s the beauty of distros, those that want traditional package structure can still use a distro that does.
Even the current flatpak first distros like OSTree spins of Fedora (Silverblue, Kinoite et al) provide mutable containers for using any package format you like.