4 ms·
> I'm using "AppImage" ... AppImage is another one of the aforementioned "vagaries of the ecosystem." No single developer can sensibly manage snap, flatpak, ap
by sgbeal 2y ago
> I'm using "AppImage" ...
AppImage is another one of the aforementioned "vagaries of the ecosystem." No single developer can sensibly manage snap, flatpak, appimage, deb, rpm, apk, and whatever other package formats de jour are common these days. The lowest common denominator is source releases.
- h2odragon 2y agoi run a debian so b0rked that apt usually don't work. AppImages do work, usually. "no single developer can sensibly manage $LIST" .. that why there's the variety of systems that attempt to avoid the laundry list. But the last time i sold software was back when "turnkey" with hardware and everything was the way things were done and we had something like 3/4 of our units ship as part of a package we integrated.
- sgbeal 2y ago> "no single developer can sensibly manage $LIST" .. that why there's the variety of systems that attempt to avoid the laundry list. And that variety further contributes to $LIST. <https://xkcd.com/927/ https://xkcd.com/927/> i'm not complaining about there being variety. i'm expressing support for the vendor's decision to avoid supporting Linux on the grounds that such variety makes it untenable for them to support. As someone who co-manages active FOSS support forums 24/7, they have my full sympathy. No matter how many OS flavors a project attempts to support, there's always that next person crying out, "but what about _my_ OS of choice?"