Does Microsoft select for assholes or something? There's a thousand other package manager names [1] in the wild and they chose that one.
So much for "developers, developers, developers"...
[1] https://en.wikipedia.org/wiki/List_of_software_package_manag...
- "NuGet" is super-popular in .NET circles (included in Visual Studio by default)
- "apt-get" is the classic tool for Windows Subsystem for Linux
So "WinGet" certainly "makes sense" as a name without being a direct ripoff of AppGet
APT is the classic tool for debian-like Linux distributions. FTFY
FWIW, I agree with you that WinGet is an entirely logical choice, catchy, and ultimately unrelated to AppGet. Yeah, it may seem like the choice was made intentionally / in spite of AppGet, but anyone who knows a bit about big company dynamics will tell you that the explanation for situations like this is usually mundane, innocent, and often dysfunctional — much like a toddler. A toddler that happens to have a billion dollars and can reshape the world with its decisions, but still similar. “The name is catchy and I like it” is akin to “I see red ice cream and I want it,” and it’s probably nothing deeper than that.
It was rather unfortunate to use apt-get as an example and then say it was for Windows, though. :)
Hello darkness, my old friend…
Context matters. That's the key point here.
Plus your two examples out of a hundred or so examples doesn't make it common either (or maybe one in a half examples since apt/apt-get/apt-cache are the three Debian programs under APT umbrella).
[1] there was no way this project was going to continue despite their nonsense about "broadening the options in the community", they knew what they were doing
Edit: Imo not a bad thing, it's just how it is. A lot of people will learn (of) Linux through WSL. Linux as a runtime.
I feel for the guy, but someone who called their package manager "app get" in 2014 when "apt get" has existed for since 1998 is in no position to take umbrage at a competing package manager having a six-letter name ending in get.
I would have preferred irrelevantGet but WinGet is unambiguous enough.
Don't work for free on proprietary systems or single sponsor opensource is a lesson cheaper learned by watching others.
Many OSS projects (and pretty much all of mine) were started to scratch a particular itch, so if that itch gets scratched by another project, I'm not terribly concerned.
It's more problematic if the competition is a half assed solution that, by virtue of being backed by a larger company, still sucks the oxygen out of the space you're trying to serve.
I thought it was better named than Chocolatey or Scoop.
Edit: plan > pun. (no idea why I wrote plan, i think I wanted to write play)
Probably, but it's not limited to Microsoft.
Any company where revenues are the highest goal (and all publicly traded companies should be this way; it's an obligation to share holders) will, generally speaking, select for assholes and sociopaths.
How strong that selection is, how pervasive, and how quickly it happens are variables in the equation, but the effect is the same, and it sucks.
Well in the author's case the tool was just as useful for them than for the others. Nothing wrong with helping the community, regardless of the ecosystem.
It's pretty compelling, I predict they will pull in a lot of Apple (who use it for the terminal) devs and make a lot of Windows first devs very happy. And there are a lot.
Btw, am I downvoted because my original comment in not constructive or do people not agree with me?
[0] https://www.microsoft.com/en-us/p/windows-terminal/9n0dx20hk...
pretty subjective, I'm guessing most people find terminal-based stuff easier/nicer on a computer with an actual keyboard, rather than a (relatively) small phone screen with a touchscreen keyboard.
I believe Termux is also pretty majorly restricted by Android 10 (can only run binary code included within the application package, so no downloading additional linux packages or compiling things locally, I believe)
'WinGet', a direct copy of 'AppGet', is not a friendly reference IMO.
On the other hand "WinGet" sounds like "wing-it" i.e. release any piece of junk and fix later. Maybe. Which TBF does seem to be how Microsoft works anyway.
It's been a while, but I managed to corrupt oneget/package management on windows within a month of it being released; I spent about a week trying to fix it and eventually figured out what the problem was (though I've since forgotten the details) only to find it unfixable without reinstalling Windows.
Unfortunately, reinstalling Windows means Office won't reactivate--I've taken it into a Microsoft store, and they couldn't help me.
Also, they have now corrected the credit: https://devblogs.microsoft.com/commandline/winget-install-le...