Nix: An idea whose time has come

Re:Nix: An idea whose time has come by 3np on Saturday February 19, 2022 @02:34AM (#30395120)

Could you be more specific about your issues with Flatpak? No idea what you’re talking about here.

[ Parent | on HN ]

Re:Nix: An idea whose time has come by 1_player on Saturday February 19, 2022 @07:07AM (#30396502)

It's trolling of the "everything new in Linux is crap" type, just check their post history. Random data loss because one uses Flatpak, seriously?

[ Parent | on HN ]

Re:Nix: An idea whose time has come by smoldesu on Saturday February 19, 2022 @08:21AM (#30396961)

> Random data loss because one uses Flatpak, seriously?

I wish I was joking: https://twitter.com/planner_todo/status/1492084099875586049

[ Parent | on HN ]

Re:Nix: An idea whose time has come by 1_player on Saturday February 19, 2022 @08:29AM (#30396998)

Ah 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.

[ Parent | on HN ]

Re:Nix: An idea whose time has come by smoldesu on Saturday February 19, 2022 @09:19AM (#30397290)

So 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...

[ Parent | on HN ]

Re:Nix: An idea whose time has come by 3np on Tuesday February 22, 2022 @03:18AM (#30425279)

You'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.

[ Parent | on HN ]