Post #948598
2026-04-05 06:57 UTC
Replies (8)
-
@valpackett@social.treehouse.systems 2026-04-05 17:49
@asie I really hope the yacht money gets used and used well.. It's quite impressive what Flatpak has already accomplished but there's so much to do still
-
@xgqt@functional.cafe 2026-04-05 11:55
@asie If we were to agree with author I find it hard to "exercise the four freedoms" (https://www.gnu.org/philosophy/free-sw.en.html#four-freedoms) with some of their points.
-
@moses_izumi@fe.disroot.org 2026-04-05 10:47
@asie I find that Wine frontends are much worse than the packaging situation, when it comes to perpetuating and causing "problems that shouldn't even exist". The common practice of giving every app it's own prefix seems to mostly be a workaround for Wine's inability to handle DLL Hell conflicts, and everything else they do could probably be implemented as plugins for your file manager/program launcher/system tray/etc. It's supposed to be one of the pillars of universal Linux adoption (especially for gaming) yet is always treated as a wierd crutch rather than a proper environment.
-
@licho@kolektiva.social 2026-04-05 08:49
@asie x86 is my container, statically linked binary is my appimage. No, jk, but sometimes it feels ppl could use a reduction in the amount of the abstractions.
-
@pinskia@hachyderm.io 2026-04-05 08:19
@asie Here is a thought, the binary incompatibles is more due to the idea of move fast and break things than folks who want the ability to recompile everything and have an init system that is modular and non centralized. Look at llvm for an example, right now you are required to have something like 4 different versions to get a system running. While with gcc you just need one version. The same is true of most other more recent c++ library. And you wonder why there is dll hell now. There was no learning from the 90s. It repeated itself. This is how docker and such came about because of dependency hell.
-
@SRAZKVT@tech.lgbt 2026-04-05 07:54
@asie ah, the weekly blog post about how fragmentation bad centralisation good the problem is that doesn't work. you cannot trust one single entity with all the power that would be given to them this way, for example flathub maintainers have time and time again shown themselves to be actively hostile to application devs the part about recompiling is also pretty much worthless, reproducible builds is specifically there to allow us to be sure the provided build is correct, without extra added things. if no one else than developers ever recompile it, we're entering a security and trust nightmare, and i want no part in it. also the electricity "wasted" recompiling is a distraction from actual electricity hogs
-
@burger@social.burgeronthe.net 2026-04-05 07:41
@asie@mk.asie.pl Every time you succumb to the fragmentation of the Linux ecosystem and tell some poor clueless kid that can't run a bash script yet that he should run Mint on his gaming desktop because it's "stable" - that's one more person that inevitably decides we're all fucking crazy and never comes back Spot on. Every distribution of Linux has their own major asterisk. If you are on Fedora you need to manually grab unencumbered patents, or if you are trying to choose an arch distro it usually doesn't hold your hand, or if you use Ubuntu they might swap apt packages for snaps that sometimes have known issues. Flatpak won when the Steam Deck shipped Flatpak as its default package manager for its desktop mode. SteamOS is by far the most popular desktop distro* and it has made its mark. *chromeOS treats its dev terminal as a developer thing, not an end user thing.
-
@aura@gts.foxsnuggl.es 2026-04-05 07:46
@asie the most contentious bit in that post is that FOSS maintainers would've prevented the crowdstrike incident when the only mechanism by which that is true is the shitty state of packaging that is also being criticized see xz backdoor being noticed in debian unstable