3 ms·

Windows packaging isn't all it's cracked up to be. There is no standard package repository, the norm is just to distribute executables of various kinds, the pro

by pekk 9y ago

Windows packaging isn't all it's cracked up to be. There is no standard package repository, the norm is just to distribute executables of various kinds, the process of building installers is not that simple... "Starting deb after and if investing on rpm failed would have been much wiser" except that Debian developers already knew rpm didn't meet their needs. But these arguments are always selectively applied to certain parties (e.g. Canonical) and not others (e.g. Red Hat).

sametmax 9y ago
Try to create an executable that works for windows 7, 8 and 10. Now try to do the same for centos, ubuntu and gentoo. Or 3 LTS of Ubuntu. Besides, deb/rpm is the perfect example of our failure as a community. To the end user, having both standards bring nothing. Neither are better than the other for 99% of use cases, and we ends up needing twice the tool, documentation and community effort that we should. And because it's such pain, any languages created their own package managers. gem, pip, goget, npm... Now we are replaying the same with flatpak/snap.
justin66 9y ago
> Windows packaging isn't all it's cracked up to be. There is no standard package repository, the norm is just to distribute executables of various kinds, the process of building installers is not that simple... After dealing with the various walled gardens and their concomitant limitations, and after dealing with any system of linux package management, the Windows way feels like some sort of joyous escape from captivity.