3 ms·

WinGet was announced less than a year ago and is still in preview. The main critiques in the article fault WinGet for lacking features that are under developmen

by jimmar 5y ago

WinGet was announced less than a year ago and is still in preview. The main critiques in the article fault WinGet for lacking features that are under development. I would also love to have WinGet working fine yesterday, but it seems like Microsoft is actively improving it.

cosmic_quanta 5y ago
Indeed, taking a look at the roadmap there's lots coming: https://github.com/microsoft/winget-cli/blob/master/doc/windows-package-manager-v1-roadmap.md https://github.com/microsoft/winget-cli/blob/master/doc/wind...
- mavhc 5y ago
  Except v0.2 is still only in preview, so it's 7 months late, on an 11 month old project
guitarbill 5y ago
Except why not build on AppGet, or acquire it? I mean they kinda half-tried, it's an interesting read [0]. Microsoft has tonnes of money. They could have probably bought AppGet outright (I assume that since the author shut it down, they weren't too attached and MS could've bought it out), saved a lot of development time/money, had something that worked, and gone from there. There's obviously more to this story, but it just seems like Microsoft don't value DevOps/automation (true from my experience trying to do CI on Windows). Think about how many man-hours both inside Microsoft and outside are being wasted by WinGet not doing these things. A colossal waste of time. So yeah, from my perspective, the criticism is entirely justified. [0] https://keivan.io/the-day-appget-died/ https://keivan.io/the-day-appget-died/
- bb88 5y ago
  > Except why not build on AppGet, or acquire it? One thing I don't like about the Apple/MS ecosystems these days is that major pieces or open source now are pretty much required for most developers to do their jobs. Yet both seem to hold hostility to open source solutions. So some still believe in MS that open source is the devil, especially if you've spent 20 years in that mindset. Example: 25 years ago in college, ssh was getting popular, and became the de facto connection tool a couple decades ago. Only in 2018 did MS finally add it to windows. And Apple has purged GPL apps from their platform and has for years. https://news.ycombinator.com/item?id=3559990 https://news.ycombinator.com/item?id=3559990 Hence the need for articles like this: https://itnext.io/upgrading-bash-on-macos-7138bd1066ba https://itnext.io/upgrading-bash-on-macos-7138bd1066ba
  - guitarbill 5y ago
    I don't want to go too much into Apple, for sure there's some things to be worried about and keep an eye out. But at least it's POSIX, so driving CI isn't awful. I agree Homebrew is a godsend though
    - bb88 5y ago
      In reality homebrew is a third-party crutch to make a broken system more palatable for developers. To my knowledge homebrew hasn't received one cent from Apple, yet most of the developers who use Macs use it. Yet, Homebrew is probably directly responsible for driving a significant amount of sales to Apple.
deleted 5y ago
[deleted]

by jimmar 5y ago

cosmic_quanta 5y ago

Indeed, taking a look at the roadmap there's lots coming: https://github.com/microsoft/winget-cli/blob/master/doc/windows-package-manager-v1-roadmap.md https://github.com/microsoft/winget-cli/blob/master/doc/wind...

mavhc 5y ago
Except v0.2 is still only in preview, so it's 7 months late, on an 11 month old project

guitarbill 5y ago

Except why not build on AppGet, or acquire it? I mean they kinda half-tried, it's an interesting read [0]. Microsoft has tonnes of money. They could have probably bought AppGet outright (I assume that since the author shut it down, they weren't too attached and MS could've bought it out), saved a lot of development time/money, had something that worked, and gone from there. There's obviously more to this story, but it just seems like Microsoft don't value DevOps/automation (true from my experience trying to do CI on Windows). Think about how many man-hours both inside Microsoft and outside are being wasted by WinGet not doing these things. A colossal waste of time. So yeah, from my perspective, the criticism is entirely justified. [0] https://keivan.io/the-day-appget-died/ https://keivan.io/the-day-appget-died/

bb88 5y ago
> Except why not build on AppGet, or acquire it? One thing I don't like about the Apple/MS ecosystems these days is that major pieces or open source now are pretty much required for most developers to do their jobs. Yet both seem to hold hostility to open source solutions. So some still believe in MS that open source is the devil, especially if you've spent 20 years in that mindset. Example: 25 years ago in college, ssh was getting popular, and became the de facto connection tool a couple decades ago. Only in 2018 did MS finally add it to windows. And Apple has purged GPL apps from their platform and has for years. https://news.ycombinator.com/item?id=3559990 https://news.ycombinator.com/item?id=3559990 Hence the need for articles like this: https://itnext.io/upgrading-bash-on-macos-7138bd1066ba https://itnext.io/upgrading-bash-on-macos-7138bd1066ba
- guitarbill 5y ago
  I don't want to go too much into Apple, for sure there's some things to be worried about and keep an eye out. But at least it's POSIX, so driving CI isn't awful. I agree Homebrew is a godsend though
  - bb88 5y ago
    In reality homebrew is a third-party crutch to make a broken system more palatable for developers. To my knowledge homebrew hasn't received one cent from Apple, yet most of the developers who use Macs use it. Yet, Homebrew is probably directly responsible for driving a significant amount of sales to Apple.

deleted 5y ago

[deleted]