News for hackers. Stuff that matters.
Re:Nix: An idea whose time has come by smoldesu on Friday February 18, 2022 @07:22PM (#30393096)
The problem as I can see it is that the "solutions" don't really work either. Here's your options, in order of viability:

- AppImage. Basically the idea of "Apps" ripped straight out of MacOS and injected right into Linux. Works fine, but clutters your home directory with Another Folder and doesn't integrate with your desktop like a native package.

- Snap. Works on any system that can install snapd, is owned by Canonical (a pro or a con depending on who you ask), but also auto-updates and has occasional performance problems. Plus, snapd is generally kinda fussy.

- Flatpak. Sandboxing taken to it's (il)logical extremes. If you like random data loss, confusing package manifests, low-performance and generally broken software, this is the way to go. Of course, most people like it when their compositor doesn't break when installing third-party programs, so they avoid it like the plauge. It's a uniquely bad format, almost worth spinning up a Linux VM to try it for a laugh. Just make sure to use GNOME, it's useless anywhere else. That's the true hallmark of a cross-distro packaging solution!

So yeah, we're probably due in for Another Competing Standard. At this point though, I think most developers are contented to just ship an RPM and an Arch package and let everyone else figure stuff out for themselves. Honestly, I prefer that approach when compared to the blasted wasteland that is cross-distro package management.

Re:Nix: An idea whose time has come by danieldk on Saturday February 19, 2022 @03:04AM (#30395260)
Flatpak. Sandboxing taken to it's (il)logical extremes. If you like random data loss, confusing package manifests, low-performance and generally broken software, this is the way to go.

Reality check: since the Steam package is broken so often on NixOS, I ended up using the Flatpak on NixOS instead (which works like a charm).

It's a uniquely bad format, almost worth spinning up a Linux VM to try it for a laugh.

I am not sure what you are talking about. It's actually a really nice format that uses OSTree.

Re:Nix: An idea whose time has come by smoldesu on Saturday February 19, 2022 @08:29AM (#30396996)
We're comparing it to Snap and AppImage. Flatpak doesn't have enough meat on it's bones (or goodwill in it's tank) to compete with the other cross-distro distribution options, and certainly not with native packages. I'm frankly not surprised that Steam is constantly broken on NixOS, Valve doesn't maintain it (and won't due to how insanely different it's concept of package management is).
Re:Nix: An idea whose time has come by 1_player on Saturday February 19, 2022 @07:06AM (#30396498)
> Flatpak. Sandboxing taken to it's (il)logical extremes. If you like random data loss, confusing package manifests, low-performance and generally broken software, this is the way to go.

Talk about FUD and taking to logical extremes. Your constant trolling on Linux threads is not appreciated.

Re:Nix: An idea whose time has come by smoldesu on Saturday February 19, 2022 @08:26AM (#30396983)
Constant trolling? I use Linux on every device I own. If you're interested in stifling democratic development and open-source discourse, there are plenty of other operating systems that can accommodate for that mindset.
Re:Nix: An idea whose time has come by 1_player on Saturday February 19, 2022 @08:32AM (#30397014)
So am I. Using Linux on every device you own doesn't automatically qualify and make any statement you utter a truth. I've already replied in the other comment why your opinion spread FUD (especially from a self-described "provocateur"), so I have no interest in engaging with you even further. Good day.
Re:Nix: An idea whose time has come by smoldesu on Saturday February 19, 2022 @11:39AM (#30398371)
Would you like to refute anything I've said so far, or fight FUD with FUD?
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.
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?
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

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.

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