If you've been following my articles as of late, you'll notice that I've been exploring (obsessing over) the world of Windows-based package managers. It's an interesting concept that the Linux world gets to enjoy to great success--the ability to download and install applications via a single program, much like how you would grab a song on iTunes or an application off its App Store.
In last week's Murphy's Law, I postulated that this exact combination of one-button glam plus a functional, community-driven application repository would be a surefire way to increase open-source awareness amongst average computer users. That, and it would offer power users a better way to grab, install, and manage large bundles of applications on any number of individual or networked PCs.
A number of you seemed to agree. That's great. But as we all saw in this week's freeware roundup, the state of the package manager market for the Windows operating system is tragic at best. It's difficult, if not impossible, to find a working package manager that fulfills the three main criteria for usefulness: updated applications, minimal downloading errors, and a halfway-decent GUI.
What's the holdup in Windows Package Manager development? Are they really that tricky to create and maintain? And why should users ultimately care about these kinds of applications? To get the answers to these tough questions, I turned to BennyP--creator and sole maintainer of the WinPackMan package manager application. He's currently caught up in bringing this once-popular piece of software back from the dead, making him an ideal candidate for learning more about what's going on in the trenches of third-party Windows package manager development.
If you're ready to discover the dark secrets that separate Linux and Windows package managers... click the jump!