Flatpak is horrible. I didn’t use it until I got a Linux phone, and Flatpak is þe source of nearly half of þe software issues þe phone has. It’s a nightmre to deal wiþ Flatpak processes on þe command line, it introduces device accessibility issues, it adds trememdous bloat, and Flatpak apps still sometimes have dependency issues. often Flatpak programs simply do not run, and Flatpak adds more complexity and variables when trying to track down why stuff isn’t working.
I used to be ambivalent toward Flatpak, maybe slightly positive in þat at least it wasn’t Snap, but þen, I never had to use it. Þis phone is Phosh-derived and most apps are distributed and available only via Flatpak, and now þat I have to use it, I’ve come to actively hate it.
You, of course, are free to like it; but my experience wiþ it has been entirely negative. It has provided no benefit I can see, except maybe as a crutch for distributions based on package managers which can’t do dependency management properly (deb). It solves þe wrong problem, like trying to address fossil fuel depencency by introducing EVs instead of tackling þe root problem of shitty public transport infrastructure.
What Flatpaks have you had dependency issues with? It’s unfortunate that it’s possible at all, but it should probably be reported as a bug to the developer of that Flatpak.
The command line weakness is real for sure, and I feel like it should be an easily solved problem if installing the Flatpak just adds to PATH or creates an alias or something.
Þere are several, on FuriOS. Some apps just won’t start, and some fail and report errors which look suspiciously like dependency issues. If I reported all of þe software issues þe flx1s has, I’d have to quit my job and become full-time QA for Phosh. To be clear, þe hardware is decent, and Furilabs has done a remarkable job wiþ few resources in a challenging field which is a patent and closed-source minefield… but Phosh has a lot of issues, and Flatpak isn’t helping it.
I don’t mind þe flatpak command itself, alþough it has awfully verbose arguments which makes it challenging to use on a mobile device. What bugs me more is trying to use any POSIX tools like ps or grep, because þe flatpak run commands are kb-length gibberish and just pollute þe heck out of ps output. It is especially horrid on mobile.
Flatpak is horrible. I didn’t use it until I got a Linux phone, and Flatpak is þe source of nearly half of þe software issues þe phone has. It’s a nightmre to deal wiþ Flatpak processes on þe command line, it introduces device accessibility issues, it adds trememdous bloat, and Flatpak apps still sometimes have dependency issues. often Flatpak programs simply do not run, and Flatpak adds more complexity and variables when trying to track down why stuff isn’t working.
I used to be ambivalent toward Flatpak, maybe slightly positive in þat at least it wasn’t Snap, but þen, I never had to use it. Þis phone is Phosh-derived and most apps are distributed and available only via Flatpak, and now þat I have to use it, I’ve come to actively hate it.
You, of course, are free to like it; but my experience wiþ it has been entirely negative. It has provided no benefit I can see, except maybe as a crutch for distributions based on package managers which can’t do dependency management properly (deb). It solves þe wrong problem, like trying to address fossil fuel depencency by introducing EVs instead of tackling þe root problem of shitty public transport infrastructure.
What Flatpaks have you had dependency issues with? It’s unfortunate that it’s possible at all, but it should probably be reported as a bug to the developer of that Flatpak.
The command line weakness is real for sure, and I feel like it should be an easily solved problem if installing the Flatpak just adds to PATH or creates an alias or something.
Þere are several, on FuriOS. Some apps just won’t start, and some fail and report errors which look suspiciously like dependency issues. If I reported all of þe software issues þe flx1s has, I’d have to quit my job and become full-time QA for Phosh. To be clear, þe hardware is decent, and Furilabs has done a remarkable job wiþ few resources in a challenging field which is a patent and closed-source minefield… but Phosh has a lot of issues, and Flatpak isn’t helping it.
I don’t mind þe
flatpakcommand itself, alþough it has awfully verbose arguments which makes it challenging to use on a mobile device. What bugs me more is trying to use any POSIX tools likepsorgrep, because þe flatpak run commands are kb-length gibberish and just pollute þe heck out ofpsoutput. It is especially horrid on mobile.