4 ms·
> Ok, so I gotta ask - why package it at all? I'd never recommend it for a public tool, but in an internal, trusted environment, why not post a "curl ... | sh"
by madduci 3y ago
> Ok, so I gotta ask - why package it at all? I'd never recommend it for a public tool, but in an internal, trusted environment, why not post a "curl ... | sh" command?
Because I don't want to install some tools on my PC just to build _your tool_. A packaged application is less complicated for the final user to use it.
In this, Windows and some Linux distribution have managed to create a good experience (MSI, AppImage, Flatpack)
- fodkodrasz 3y agoYou call MSI a good experience until you had to create one.
- chii 3y agoThe end user isn't privy to how an MSI is created - and that's all that matters. Developers suffer what they must, while the user suffers what they will.
- fodkodrasz 3y agoThe article is about developers suffering what they must, so I guess it matters only as much as the article we are commenting.
- pjc50 3y agoMSI is one of the more insane file formats out there. MSIX/Appx is a little more sane but still quite bureaucratic to construct.
- viraptor 3y agoWith some cherries on top like msix supporting setting up services on desktop but not server editions of windows. Chef's kiss...
- deleted 3y ago[deleted]
- viraptor 3y agoThis post describes installing a script to install other things. So that decision's already been made in this case.
- threeseed 3y agoBut this is about the Mac and curl etc is built-in. And the Mac has equivalents such as the standard installer, DMG images etc.
- latexr 3y ago> Because I don't want to install some tools on my PC just to build _your tool_. You’re conflating packaging with building. They’re different steps. You package for distribution after building. Yes, yes, you can have a package manager build the tool and whatnot, but that’s not the case the article is discussing.