3 ms·
Could you be more specific about your issues with Flatpak? No idea what you’re talking about here.
by 3np 5y ago
Could you be more specific about your issues with Flatpak? No idea what you’re talking about here.
- 1_player 5y agoIt's trolling of the "everything new in Linux is crap" type, just check their post history. Random data loss because one uses Flatpak, seriously?
- smoldesu 5y ago> Random data loss because one uses Flatpak, seriously? I wish I was joking: https://twitter.com/planner_todo/status/1492084099875586049 https://twitter.com/planner_todo/status/1492084099875586049
- 1_player 5y agoAh because of a bug in an app (or it's packaging), the whole flatpak ecosystem is corrupt and causes data loss? How is that different that someone mistakingly causing an rm -rf /home in an RPM post-install script? Try again.
- smoldesu 5y agoSo now we're blaming developers for messing up with sandboxed systems? I really hope this isn't the rhetoric you use to convince people to start packaging with Flatpak...
- 3np 5y agoYou're the only one assigning blame to anyone here. Not all problems need a villain. Both of these things can be true at the same time: The library authors ultimately messed it up and could have prevented it by reading documentation better. Flatpak has a footgun and could have prevented it by better dev UX and/or structuring docs differently. Hopefully this incident is leading to improvements in both.