10 ms·
What you're saying is it's a walled garden, an app store. Well then it sucks because of all the problems with those, including but not limited to not being very
by AnIdiotOnTheNet 9y ago
What you're saying is it's a walled garden, an app store. Well then it sucks because of all the problems with those, including but not limited to not being very open for developers to get into without jumping through hoops and therefor having limited application choices based on whatever the package repository maintainer decided to do or not do.
All packages including their dependencies is the right way to do it (AppBundles, AppDirs, PortableApps, whatever you want to call that methodology). It's 2017, you can't tell me that sharing a 400k libsomebullshit.so between the 2 applications that use it is worth all this added complexity.
Bonus: It's easy as hell for developers to deploy this way. Of course, it does require a defined and stable base system to rely on, and we know how much the Linux community loathes that concept.
Still, kudos to AppImage for at least trying to do the right thing.
- Dylan16807 9y agoHuh? Package management doesn't imply a walled garden. You can install packages from anywhere. And nothing stops you from having each package install into a single folder, if you want clearer boundaries. Sharing a 400KB library is no big deal, but I don't want a dozen 200MB python installs, etc.
- AnIdiotOnTheNet 9y agoPackage management very much does imply a walled garden. You can install packages from anywhere... as long as they conform to your package format... and they aren't incompatible with the way your distro's repository does things... and they aren't too old... or too new... did we mention there's like, 200 distros? Yeah, totally flexible that. And since when the hell can you choose where to install packages? Unless you're talking about very niche things like GoboLinux, or stupid workaround shenanigans with chroot and/or large amounts of symlinks. It's possible this is a thing that has changed and I never noticed because nobody ever does it. However, I doubt that very much given OSS developers' love for hardcoding paths at compile time. People routinely distribute Electron Apps, which are bundled with an entire browser. Minecraft comes with the entire JRE bundled. Doom 2016, as far as I know, doesn't do anything like that but is something like 70GB anyway. 200MB is not a big deal, and for my money the complexity and limitations introduced by a package manager more than outweigh the extra space lost in the few cases where a large dependency might be used by more than one application.
- Dylan16807 9y ago> You can install packages from anywhere... as long as they conform to your package format... and they aren't incompatible with the way your distro's repository does things... and they aren't too old... or too new... You have to have a standard to make it work. But you need standards to make portable apps work too. There's no reason a package standard has to be more complex. > And since when the hell can you choose where to install packages? My argument is that it's possible to make a package standard that can do it, and be simple. It's not inherent to package managers that these things be hard. > the complexity and limitations introduced by a package manager more than outweigh the extra space In some cases, sure, but I'd have a bunch of OS installs that suddenly triple in size or more and that's not worth it to me.