3 ms·
I think you’re overestimating how generic package management is. They’re very tightly coupled to their respective languages and build systems.
by HeyImAlex 5y ago
I think you’re overestimating how generic package management is. They’re very tightly coupled to their respective languages and build systems.
- scrollaway 5y agoI worked on the problem for two years. I'm not overestimating anything; it's just that the wrong targets are being set. Like I said in my post, it's a "single package manager to rule them all" is the wrong goal. What you want is a common protocol, and multiple implementations of it. "I want an app store" = spin up your favourite PackManProtocol server, configure it to your needs, done. The basics of package management are all very similar and can be covered by core use cases. The solution would need to be extensible enough to be usable beyond those. But having restrictions can also be good for an ecosystem (preventing weird-feature creep).