zlacker

The really sad thing is that I still don't think Microsoft has actually solved the package manager problem in any meaningful way. WinGet feels like just yet another subtly incompatible package standard.

I would say Microsoft should buy Chocolatey but they would probably just ruin it. (Not to say this is a uniquely Microsoft problem; it's reminiscent of the Pipenv/Poetry/virtualenv... mess in the Python community.)

>>lukesc+(OP)
I'm convinced the sole purpose of some open source projects are to be good enough to prevent other open source projects from filling the void, but bad enough to keep from competing with vested commercial interests.

This might just be one of those cases. Why would Microsoft want to invest in another distribution platform when they already have the Microsoft Store where they can do whatever they want?

Sure, WinGet has an MIT license, but that doesn't mean anything. The only important thing is who gets to commit to the manifest(s) on the master branch. That's Microsoft. They own it. They control it. They curate it. They decide who gets to distribute via it.

I'd bet money they'll tie it in to Azure somehow at some point.

>>ryan29+O2
Microsoft is likely looking for a solution that would allow easy distribution of software in enterprise context without having to repackage it.

Having a widely accepted and used package format would solve that. You could just pick the package for notepad++ and others and push them to workstations via Intune.

>>jpalom+Bd
They already have MSI though?

>>throwa+Pf
There were attempts, but never any followthrough. Even MS doesn't distribute all of its software as MSI.