Replies: 3 comments
-
I'm all behind where they're heading. I've talked briefly to Rich Turner about it, and I'm really quite excited. I think they're going to be able to succeed where I was not able to. Had I not been extremely involved in where I am now, I heavily considered going to work on this. Very very excited |
Beta Was this translation helpful? Give feedback.
-
Per https://devblogs.microsoft.com/commandline/windows-package-manager-preview:
https://chocolatey.org/pricing Of course, advanced features would take time to implement. |
Beta Was this translation helpful? Give feedback.
-
Looks like they reached out to them https://keivan.io/the-day-appget-died/ |
Beta Was this translation helpful? Give feedback.
-
I feel like we've been here before it seems with Windows Package Management using the OneGet Project (https://docs.microsoft.com/en-us/archive/blogs/packagemanagement/introducing-packagemanagement-in-windows-10) & https://github.com/OneGet & the well used and maintained Chocolatey application that has been in use for over 4 years now & already has tremendous experience with package management on windows and have a decent trajectory going forward.
So considering that there is a product well used out there, what benefit do I as a user of Chocolatey get moving over to winget?
What is the incentive to be invested in this going forward as opposed to Chocolatey?
Also as a wider query with this did anyone reach out to any of the contributors/original authors on OneGet like @fearthecowboy @jianyunt, Chocolatey like @ferventcoder or the PowerShell team like @joeyaiello @SteveL-MSFT about this to gain some direction on where they have had pain points with this in the past? If not I'd recommend you look at involving them (if they can find the time) as a steering group if you really want this to be a real long term success.
Beta Was this translation helpful? Give feedback.
All reactions