zlacker

In all fairness:

- "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

>>TAForO+(OP)
Wait! apt-get is not Microsoft's invention https://en.wikipedia.org/wiki/APT_(software)

>>TAForO+(OP)
> "apt-get" is the classic tool for Windows Subsystem for Linux

APT is the classic tool for debian-like Linux distributions. FTFY

>>TAForO+(OP)
Your point is solid ('get' is a common name for packaging systems) but if you're not familiar with Linux, apt-get is from Debian.

>>TAForO+(OP)
I’m not sure you could have illustrated their point more perfectly than this. But please don’t feel like people are amused at your expense — it’s just such a perfect demonstration of exactly what they were saying.

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. :)

>>TAForO+(OP)
> "apt-get" is the classic tool for Windows Subsystem for Linux

Hello darkness, my old friend…

>>TAForO+(OP)
It still looks really bad. If you're going to copy and kill off [1] an OSS project, when you're a major company who owns the platform, with a long history of this sort of thing, after baiting the developer for information, then copying the name on top of it is just cruel and in poor taste.

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

>>banger+e6
Get used to it, this is going to be the bulk of the "Linux" users from now on.

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.

>>deno+Wb
Yeah I hope the TLD read is that this article has nothing to do with Microsoft embracing Linux and Debian distribution related tools are safe?

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.

>>TAForO+(OP)
This comment should have a dualised state: downvotes that push it higher and upvotes that push it lower.

>>teeker+Vh
Considering the fact that there are five times as many Android devices as Windows devices, and the greater ease of use of Termux compared to WSL. I find that highly unlikely. Anecdotally every newbie programmer I've seen try to use WSL has just ended up installing Linux in frustration.

>>dmix+dg
> If you're going to copy and kill off an OSS project

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.

>>foolme+Nk
> Don't work for free on proprietary systems or single sponsor opensource is a lesson cheaper learned by watching others.

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.

>>knolax+Yn
Termux is a terminal emulator, WSL is a subsystem. Did you try [0]? And WSL2?

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...

>>knolax+Yn
> greater ease of use of Termux compared to WSL

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)

>>teeker+UF
Termux is a lot more than just a terminal emulator.

>>teeker+UF
By the way, every terminal application you're used to (Terminal.app on macOS, iTerm, the Windows Terminal, Ubuntu's Terminal application) is a terminal emulator. I've tried WSL1 and 2 and couldn't get past the typing latency, awful font rendering, incredibly slow downloads, apt/dpkg bugs, and not syncing with the actual filesystem like Linux/macOS do. For example, I like to copy my dotfiles to ~/Dropbox/dotfiles. This isn't possible on Windows, and if you force it to do so it will corrupt the files.

>>teeker+UF
I doubt it pulls in anybody in the unfinished state its in. WSL does not integrate very well and is miserably slow. My 13yo thinkpad runs circles around WSL running on my workstation. WSL2 is still beta, and given how buggy 1909 still is, I am not installing 2004 on anything I care about. And I recently tried Windows Terminal, but it couldn't even give me an admin prompt without giving every single session elevated privileges, so I gave up after 5 minutes.