Windows Package Manager 1.0

devblogs.microsoft.com

12 points·lame-robot-hoax··8 comments

Does Microsoft make any attempt to explain why someone would want to switch away from Chocolatey and use this? Until someone can make that case I'm sticking with choco.

Packages have names like "Microsoft.WindowsTerminal"? Is it vendor, period, OS, then the name of the package? Or something else? I'm already confused.

Even when Microsoft is incredibly late to a game, they still manage to recreate the proverbial wheel while happily ignoring tons of lessons which everyone else already figured out.

Also, apparently this doesn't even handle compiling, so this is only a tool to install pre-compiled packages. And there's a whole list of "Scenarios" that looks like an "action" list that came out of a meeting where managers did most of the talking.

Oh, Microsoft.

Microsoft is horrible at naming things. The one time they had a product with an awesome -- Silverlight -- name they cancelled it.

(Of course they also recycle product names so Silverlight will probably come back but knowing MSFT it will be attached to something that sucks.)

"Windows Terminal" is the name of the application.

And everyone is so excited that Microsoft finally decided to graciously add a package manager to their flagship OS.

The other thread currently has more comments: https://news.ycombinator.com/item?id=27292654

Scoop is awesome!

YES! And also, scoop is much simpler and open - all packages go to a simple and accessible user folder, and it also can unzip files.

Reply on news.ycombinator.com