What is Reddit's opinion of
Windows Package Manager CLI?
From 3.5 billion Reddit comments
➔ Windows Package Manager CLI website
By popularity on Reddit, this Service is:
76 reviews of this app found across Reddit:
Remember this is a preview :) We are doing this in the open. If you have feedback or suggestions, please create Issues: https://github.com/microsoft/winget-cli/issues. The decision was to be open source rather than try to show up with a fully baked product that didn't do what you wanted.
To be fair, for edge specifically, you can just get <code>winget</code> and type winget uninstall microsoft.edge
The only thing that breaks is the Help from the web links which tries to open in edge rather than your default browser
We're on version 0.1.0 doing this in the open. We'd love your suggestions and feedback: https://github.com/microsoft/winget-cli/issues/new/choose
Most of the regular package manager functionalities including uninstall and dependency management are listed as scenarios for v1.0. Let's see what they deliver when that is released (around Spring 2021).
you can install winget from github and winget is also single command line.
I don't see how it's more complex to install that chocolatey.
The manifest spec clearly supports "well-known" installer technologies like MSI, MSIX, inno, Nullsoft, etc. That's a bit better than just downloading arbitrary EXEs.
With that in mind, it's not too hard to imagine that the v0.1 spec is eventually revised to include uninstall information. It'd be bonkers to not offer uninstall functionality. That's why you would specifically include MSI, Nullsoft, etc. because those have well-known uninstall switches etc. Yeah, you have to trust the installer and uninstaller are doing what they say they do, but that's no different than the case on desktop outside of winget
Hopefully this is just the package description format that allows that sort of thing for a transition period until more "native" winget packages with dependencies happen. Otherwise I don't really understand this. The purpose of one to me is to manage dependencies and know how to install and uninstall things yourself without installers and do complete uninstalls without breaking other things.
So many essential features coming for V1.0 that I guess I'll just wait for that one instead. But good to hear this glaring hole in the Windows ecosystem is going to be fixed in an official fashion. Combined with .NET 6 and true cross-platform UI development also targetted for late 2021, interesting times ahead and especially in that timeframe.
It's currently v0.1. The v1.0 milestones seem to make it a more fleshed out package manager: https://github.com/microsoft/winget-cli/blob/master/doc/windows-package-manager-v1-roadmap.md#v10-scenarios
Or maybe MS should just fix their automated Store certification process because FYI, we already have a submission QA especially for apps with similar names in winget. The process is half-automated by a bot that automatically adds a PR comment for app manifests with similar name to an existing, verified package.
https://github.com/microsoft/winget-cli
There is ABSOLUTELY ZERO reason why Store certification process should be LESS SECURE than winget.
The community can help but man, they already relegated Windows QA to the Insider community and now they will also relegate cleanup of a proprietary app store to the community? Dude, they should just open source Windows at this point if the community is the one who will always do the dirty work.
link: https://github.com/microsoft/winget-cli/releases
And winget is more for the admin and console crowd. The target audience for the store would not feel at howm with winget or is there a GUI for winget now?
> I don't know why people are using Linux
Lots and lots of different reasons.
- Tinkering. Most of the stuff that goes into Linux and the userspace programs that run on top of it is open-source. So if you're running a program and wonder, "Hmm, I wonder how it does that," it's often possible to look at the code yourself. Similarly, if you don't like a certain aspect of the interface, there's often a replacement out there, or you can write your own.
- Package managers. Windows is finally looking at adding a feature that Linux distributions have had for more than 25 years.
- Building software. While it's easy to write code within the Microsoft ecosystem with Windows, a lot of other languages' tools aren't built with Windows in mind. I've been messing around with Idris lately, and it took all of five minutes to install the dependencies, build the compiler, and start working. Doing the same on Windows is significantly harder. In many cases, the tooling on Linux is so much better than Windows that Microsoft created WSL to use those tools on Windows.
- Server administration is a lot more straightforward on Linux.
https://github.com/microsoft/winget-cli/blob/master/README.md >At preview you can search, show, and install packages.
>preview
>Soon we will have to uninstall, list and update
>soon
LMAO HAHAHA
>Data/Telemetry
>This project collects usage data and sends it to Microsoft to help improve our products and services
OHNONONONO HAHAHAHAHAHA
On windows:
In order of personal preference and availability of packages.
These apps help you install other apps SUPER easy. No more dialog boxes. No more clicking next, next, next, agree, next, next, ok. I have not installed anything manually in like 3 years.
They all download and install stuff for you automatically. No hassle.
Did any of you that are complaining read the Roadmap ?
They are going to add (uninstall, update, dependency support etc.. )
It's in its very early stages but it's being developed in the open pretty much from the beginning with and is open for contributions like a regular old community FOSS project which I find pretty cool.
Package manager repo: https://github.com/microsoft/winget-cli
Packages repo: https://github.com/microsoft/winget-pkgs
"Packages" are YAML files with metadata and a URL to the installer.
This means it's not a repo of scripts which build redistributable tarballs like (most) package managers on Linux have done for decades, but a repo of installers.
This isn't ideal of course but it's orders of magnitude better than what was there before (nothing).
Let's see where they take it, they seem to be pretty keen on letting the community help them do it properly.
Yeah, this is a massive game-changer. Folks that aren't hyped for this likely aren't that familiar with package management systems.
We can create custom repos as well, per the documentation. This is a godsend for developers (and IT for various reasons).
The github is over here.
Ninite about to disappear though. lol.
Jesus Christ, what shitty ass bank do you use? They've had like, a decade to figure this out.
Seems like you've figured something out, but for future reference I think if you uninstall Edge with Winget (install the msixbundle I linked then type "Winget uninstall Edge" in command prompt) and don't have any other browsers installed, it'll use IE as a fallback.
Sure, if you meant just latest version of windows 10 home/pro, there is couple of ways. You can install preview version of Windows App Installer (probably need registration), or you can just downloade it from github
Theres another method you can try:
1- Install winget from github; direct link: https://github.com/microsoft/winget-cli/releases/download/v1.0.11451/Microsoft.DesktopAppInstaller_8wekyb3d8bbwe.appxbundle
2- Open powershell as admin and type: winget uninstall appname (ex: winget uninstall cortana)
Should do the trick.
From the Github page: https://github.com/microsoft/winget-cli
> The winget.exe client is instrumented to collect usage and diagnostic (error) data and sends it to Microsoft to help improve the product.
You can build and disable this, but I am concerned about the default installation later (its opt-out, not opt-in). Everything you install and use will probably be collected as usage data and sent.
https://github.com/microsoft/winget-cli/blob/master/privacy.md
> There are also some features in the software that may enable you and Microsoft to collect data from users of your applications.
Indeed, Linux is pretty good these days. I however was just trying to point out that Windows has recently been trying really hard to work more like a Unix/Linux system. They are even adding a proper package manager.
Hi. Microsoft PM working alongside winget team here.
Agreed. Most Windows apps are shipped as self contained units, including all the dependencies they need to run.
Part of the reason for this is because Windows lacks a Package Manager with full dependency resolution.
Perhaps if winget one day supports full dependency resolution that will start to change, and apps will be able to ship with 100 dependencies and all must be accessible and available for an app to install. But that'd need a mature and complete PkgMgr and ecosystem. This may happen over time. If it's what you want to happen, then sound off in the repo: https://github.com/microsoft/winget-cli
Thanks for the info - always happy to learn new stuff. Does any of the stuff on their road map address the major concerns you have? https://github.com/microsoft/winget-cli/blob/master/doc/windows-package-manager-v1-roadmap.md
https://github.com/microsoft/winget-cli
It works, but it's just an installer-executor like Chocolatey rather than a package manager like Scoop. Still, if you have installed stuff with their installer, Winget will work just fine to update (aka reinstall) them.
Stumbled on this when I was curious and typed "install deltarune" into winget.
Winget listed it as "Fangamer.Deltarune" so it does seem to be a legit source still.
Edit: Just discovered if you type "Winget Show Deltarune" the version listed is "0.6.6.6". How spooky.
do those winget packages have dutch support?
but at a quick glance there are not language setting set anywhere
I did see this
https://github.com/microsoft/winget-cli/issues/238
and this is his web post about it
You have some options to autoupdate with package managers:
- Chocolatey · https://community.chocolatey.org/packages?q=HWiNFO
- The recent winget · https://github.com/microsoft/winget-cli
- Also Scoop · https://scoop.sh
You can't have the cake and eat it too, so no GUI.
Hello
Download and install the package from there:
Release Windows Package Manager v0.3.11102 Preview · microsoft/winget-cli · GitHub
​
Friendly greetings
>I still don't know how to build it.
Don't need to! Just grab the appxbundle from the releases page and install it.
I can't recall whether installing was just a doubleclick on the downloaded file, or if I had to use Add-AppXPackage. Either way - not as complicated as having to build it yourself :)
Microsoft is developing an official windows package manager: https://github.com/microsoft/winget-cli
​
I hope it turns out well because I love Linux for its package management, regardless of Linux distro I always found the package manager way easier and faster than installing things manually. I never tried chocolatey on windows but I've heard good things. And where I use package managers for developing (npm, nuget, pip, composer) I have always liked the experience far more than hunting down minifieds/dlls and pdbs/wheels/whatever the applicable format for the platform.
I haven't looked at it for a while, but a while ago I found these issues: https://github.com/microsoft/winget-cli/issues/179 https://github.com/microsoft/winget-cli/issues/279
There's an opt-out by now (not sure how obvious that is from the documentation, though), but considering MS's track record, I take little stock in it being completely telemetry-free with this option.
I'd like to suggest also "winget", you can create a script with it that will install all the software you select, and it has a lots of software.
Originally winget is a windows package manager, you can install software via CLI (similar to Linux distro).
Links:
P.S: You can create the script on the second link, just "add" all the software
Kind of, but no. It is Microsofts own thing: https://github.com/microsoft/winget-cli
And thanks for making me look that up, looks like I finally won't need an Insider build. (Or I misread the last couple times.)
Either user needs to be local admin and the app needs to be run in user context instead of system, or you work around this by letting the system look for the appinstallercli.exe and execute it as system:
https://github.com/microsoft/winget-cli/discussions/962#discussioncomment-1634178
Yeah I changed it to run from the WindowsApps folder because some apps like 7-zip won't install if they're run from a user context which is what winget defaults to. I found a comment from rothgecw in this thread where she explains how to call winget using the system account. If you install it using the system account then all users can use it, and so far it seems that apps that are user profile specific, like Slack, also seem to install under the system context.
The detection script is where I ran into some issues. I wasn't able to use winget in the system context to detect whether a program was installed. So I have it checking the uninstall registry folder, and the Installer registry folder. Most apps seem to have some data stored in one of those two places but I've only tested the 21 programs we have deployed through winget.
For the deployment failure it might be a bit of a cascading failure from those weird spaces from winget show. I'm still pretty new to powershell so I'm struggling a bit to clean up the results from winget show and get them into a usable format. Right now I'm creating a custom psobject and adding the output to that, but I might look into a different way of porting that information into the form.
Neat! Make sure to install Winget from the Github page since the only other option is the Windows Store, which we don't have on LTSC.
From the latest release download the .msixbundle and .xml file.
Make sure you have the VC++ v14 Desktop Framework Package installed first and foremost.
Open PowerShell and run (replace file paths to correct locations):
Add-AppxProvisionedPackage -Online -PackagePath PATH TO MSIXBUNDLE -LicensePath PATH TO XML -Verbose
Wait for install to finish and you're done.
Next up I like to browse programs on winget.run and use the 'copy command' button to make pasting to my script easier. If a program I need isn't available on Winget I add the name of this program to the top of my script as a comment: ```ps1 <# Not available in Winget: Adobe Creative Cloud MSI Afterburner ThrottleStop
>
... ```
Hey I wanted to follow up on this and say we ended up running into the same issue. rothgecw ended up finding the solution that worked for us
https://github.com/microsoft/winget-cli/discussions/962#discussioncomment-1561274
Not windows store, but yes a package manager of sort by ms for windows, like chocolaty or scoop. Uses github to manage the community repos
I ended up moving in a different direction.
Looks like Microsoft implemented a REST API for 3rd party repo support: https://github.com/microsoft/winget-cli-restsource
Winget made by Microsoft is an open source command line program that allows you to uninstall any program on your PC except Windows Defender.
I use it to uninstall even things you are typically not able to like Cortona, Your Phone, Etc.
I do not suggest installing extra software for this task. However I suggest you install software using Microsoft's own winget-cli. Install software from without additional checkmarks
The last time I looked into this, the problem was that the winget command could not be executed as system-account (the way intune and sccm deploy their stuff).
So if MS didnt change something, the command needs to be run as the user with administrative rights.
Download the Desktop App Installer and install it:
When done, try to install one from the mentioned apps again.
The thing with Windows 10 vs 7 is that while 10 definitely has a lot of advantages (and, y'know, isn't EOL) the advantages are also very boring. "Ooh, plug and play works a lot better on Windows 10!" doesn't really get people going, y'know? And sometimes the good parts are also pretty directly linked to the shitty parts, like with Windows Update.
Ultimately it's a sometimes annoying and frustrating but ultimately more robust and stable OS. All your modern software and devices will work much better with 10 compared to 7, the security is much beefier, and quite frankly a lot of problems with Windows 10 do tend to get blown out of proportion. (Cortana isn't even enabled by default anymore, and yet I still see people mad at its existence.)
And it should be noted that Windows 7 has plenty of telemetry in there, too - Windows 10 just made it more obvious. And Microsoft has actually gotten quite good at being transparent about what they're collecting and why. While I think some of the "Optional" diagnostic data they collect is definitely a bit invasive and creepy, I'm actually fine with the "Basic" settings - nothing there really jumps out at me, and it all does seem to be primarily used for diagnostics info. Lots, and admittedly I do mean lots, of "What is this setting at?" and "What hardware configuration is this" kinda stuff. What you're okay with might differ, but it's worth looking through it all anyway. (And I don't recommend "Windows telemetry remover" programs. They can cause a lot more problems than they solve.)
Though, if you do want something cool that isn't in Windows 7, might I recommend installing winget? It's been a real game changer for me.
It's in "preview", essentially beta. It is not pre-installed with Windows, you have to download it from the GitHub Release page here:
It has come a long way quickly and is quite promising. I use a combination of winget and scoop on Windows.
Winget is more like apt/yum in that it supports official releases of software and pushes you to update software that is not the latest release.
Scoop is more like homebrew, more for developers than end users and allows multiple side-by-side installations of a huge range of tools, but they don't install in the traditional sense so they won't be available in the Programs list in settings.
Chocolatey is good, and if used in a production environment you are best maintaining your own repository (for supply chain security reasons).
One thing to keep an eye on is Microsoft's winget. Based off 'AppGet' but unfortunately MS don't prominently allude to winget's origins, although they have offhand mentioned it.
It's no where near Chocolatey IMO (yet), but I image I will get close and overtake eventually.
Major features in progress or on the backlog are:
Native PowerShell support. Yep, you heard that right, MS released a 'new' tool and it isn't PowerShell native, it's an .exe and takes command line arguments and outputs to standard output (because of course it isn't actually new).
Microsoft Store support. Yep, can't install app from the Microsoft Store with Microsoft's new package manager.
Custom repositories. Public one is on GitHub
Winget isn't powershell, though. Don't confuse it for PackageManagement (used to be OneGet), which was the powershell-based package manager manager. Winget is its own standalone thing that was ridiculously unnecessary but people never did grok OneGet so I guess it had to change.
The only way to add more details to the output would be to change the source code.
Import-Module $env:SyncroModule Add-AppxPackage -Path "https://github.com/microsoft/winget-cli/releases/download/v1.0.11692/Microsoft.DesktopAppInstaller_8wekyb3d8bbwe.msixbundle"
and then
winget install Microsoft.Teams --silent
yes I did, did you?
Also check your links again, it redirects to error page.
this is the github page
there are 2 ways of getting it,
- from microsoft store, but you need to join insider program
- manually from github, but you don't get automatic updates for winget
I went to the GitHub repo Winget and I installed the package manager. With that out of the way, I created a batch script that calls: winget install --id "id of the application". I can get any id by typing winget search "app name" and it will give me a complete list of apps with their ids that are called "app name"
You can download it here: https://github.com/microsoft/winget-cli/releases/tag/v1.0.11451
Then, you just use commands like winget install discord and winget uninstall Microsoft.Edge
If you can't find a package, you can also run winget search <application name>
Mate I have no idea what you're droning on about. I simply went to this link and installed the latest version of "App Installer" from there and got winget.
most people use mac / macOS from my experience, UNIX / POSIX (which is what linux and macOS is) have been the de-facto operating system used by universities and research organizations since the 70s or 80s, which is what all the early users and inventors of the web used.
POSIX-compliant / unix-like systems (Linux, BSD, OSX) have the following advantages:
- package manager: windows has chocolatey and scoop which doesn't have range of available things as on Arch Linux, Ubuntu, OSX (via homebrew). Windows now has a native package manager. but if I recall this is not available for most windows users, my windows computer can't use it.
- unix tools / environment: So much software is built on top of them that a lot of stuff you can't run, if I recall their is no native windows installation for ruby (which means also ruby on rails), you have to install cygwin or WSL, which both have a myriad of problems (you can't use docker or systemd on WSL and cygwin I recall being extremely annoying).
If you are doing front-end stuff you should have no problem but traditional back-end is annoying.
The path I recommend is to use VS Code (which is the best editor on Windows IMO), and remote access a cloud hosting / VPS provider (like linode or digital ocean etc) to do back-end stuff.
I know this doesn't directly answer your question about a Time Machine equivalent but this might still meet your needs to quickly install apps again.
Microsoft recently released a Windows Package Manager called winget.
You can, for example, install firefox by running "winget install Mozilla.Firefox" or search for an app using "winget search 1password"
Someone created a webapp that you can use to bundle up a list of apps you want and it gives you the command to run in the terminal.
References:
I mean, I know its part of the joke and all, but I use Windows at work and at home when I play games and it is so much worse there than on linux. Winget and other package managers make it easier to live with though, but like, Windows users be like (on a new install):
> Open internet explorer (or go through the personalization of Edge)
>> Kill Edge reccomendation or bing search reccomendation
>
> Open google.com (or better yet, another search engine)
>> Accept the conditions to use the site (if google); they now own you
>
> search for browser
>> Find the real result and not the ad
>
> Open site, click download and hope its the proper one
>> E.g. Google chrome has a hidden offline installer, but don't wanna tell you about it
>
> Install browser
>> Say no to Edge reccomendation
>>> Hope Windows respects your default program setting when it wants to update
>
> Tada!
Linux users be like: > Open terminal (If you don't like firefox, which is normally bundled with most distros) > > Run whatever package manager they use and whatever browser they want (e.g. apt install firefox) > >> Watch it install > > Set as default browser if it asks > > Tada!
Sorry, I just find it to amusing to not say anything :P
If you are in the Insiders Windows Package Manager program then the store will install it for you. Otherwise you could install it from Github here https://github.com/microsoft/winget-cli/releases
I don't know if it will make it, but the plan has been to include it in the spring 21 update.
For Windows, there has been a third party package manager based on Powershell around for some time now called Chocolatey. It works pretty well. There is also winget from Microsoft which is in development/preview and is open source.
https://github.com/microsoft/winget-cli
Just some stuff I have used as a Linuxadmin who finds himself using Windows frequently.
I looked into the situation a bit more and I don't see the problem with what Microsoft did with that.
Their HR failing to follow up on reimbursement for him is definitely a dick move, but it ultimately still falls on the interviewee to get reimbursed for travel expenses for an interview if it was not paid for up front. It is very easy to understand how a loosely made promise in an email can be forgotten about.
What it looks like that happened was:
- Dev makes an awesome Open Source package manager solution for Windows
- Microsoft likes it, and offers to hire him to work on the open source project full time
- Dev fails Microsoft's hiring process (or turns it down or something else, but basically for some reason the hire fell through and dev does not get hired)
- Microsoft decides to fork the project and work on it internal and make their own version of it
AppGet is open source (Apache 2.0 license), there is no plagiarizing or "stealing" here. Open source exists for you to take the code, copy it and build something else that fits your needs. They are not even required to do an attribution to the original creator, but they still did:
> We would like to thank Keivan Beigi @kayone for his work on AppGet which helped us on the initial project direction for Windows Package Manager.
It does look like the attribution came ~1 week after the original devs blog post, so they could have been better about the attribution sooner, but at least they were pretty quick to get it in there afterwards.
https://github.com/microsoft/winget-cli/commit/ed545f996acd36e9b4b277949abc7f62e259ad68
Microsoft is actually working on an official package manager called winget, still pretty early but is nice to see them working on features like this.
https://docs.microsoft.com/en-us/windows/package-manager/winget/
https://github.com/microsoft/winget-cli
Like the idea of windows having their on package manager but this concerns me https://github.com/microsoft/winget-cli/blob/67800b07618b5b03263aa6da9ee21f6b06227351/src/Telemetry/MicrosoftTelemetry.h although you can apparently opt-out of it.
Rant:
It's a weird side effect really, on one hand GOG is trying to funnel everything through their UI, Epic is acting as a key seller with a better slice for Ubi, but the mechanisms joining it all together are lacking.
Once you've bought a key/license on Epic and you start the install within the EGS client it wants to connect to your ubisoft account, but when that's done you can cancel everything in EGS and forget about it, then do everything from that point on in Uplay.
The EGS integration is a bit worse than how steam does it, EGS will often download an old version of the game which Uplay will then need to update (more data), where for ubi games on steam they just pass all responsibility for downloading/updating to steam
And the moment anyone tries to slap a standard on it all I bet it would be like reservoir dogs. The stores/accounts and money side I can understand everyone wanting their own turf, but everything else should be a solved problem by now. IMHO it should be handled by the OS with a behind the scenes mechanism like winget with the optional ability for online licenses to be plugged in
> Uses both Linux and Windows
-Linux: yay -S brave-bin -Windows: choco install brave (Also Microsoft is making winget a thing)
> OP thinking CLI is a Linux only thing
Use Playnite to keep track of different libraries so you don't accidentally buy a game on Steam that you already claimed on Epic. You can easily install common software like Playnite with a single command using <code>winget</code>.
GitHub - microsoft/winget-cli: Windows Package Manager CLI (aka winget)
I think just linking you the github is easiest, it'll have all instructions etc and a link to the repository to see what packages are available.
Here's the actual project page. It looks like they haven't hit v0.2 yet, which means they're behind schedule, but v0.1 worked for the stuff I tried installing, and there are a lot more packages in the repo now than there were when I first heard about the project.
Do yourself a favor and install winget (Microsoft's new package manager) if you don't already have it. It may or may not be preinstalled, I don't remember. Then you can install 7zip like this:
winget install 7zip
Warning: snapd pedants will try to argue that snapd itself is open-source. Reply to them that 𝖜𝖎𝖓𝖌𝖊𝖙 is open-source too (MIT license) but that doesn't magically make Windows an open and friendly system.
It works fine for developing Windows programs. It's just a pain in the ass to set everything up due to the lack of package manager. Which Microsoft is also fixing.
You can use MSFT's new package manager [1]. Okular is in there [2]. Or you just pickup the binary URL from the package file.
Its not official, but there is at least a glimmer of hope:
https://github.com/microsoft/winget-cli/issues/221#issuecomment-637877562
There have been attempts to bring Linux-like package management to Windows, eg Chocolatey and Scoop. More recently, Microsoft announced Winget as an official Windows package manager, but it's most certainly not mature enough for production use yet (no method of upgrading installed packages, or possibly even uninstalling, and the package library is still very light).
As for 3rd party libraries, I usually use the language's standard package manager for that; pip for Python, NuGet for .NET, npm/yarn for Node, Composer for PHP, etc.
> Chocolatey
It's around a year from being prod.
I don't have enough deep knowledge about Windows applications and executables and all of that to speak intelligently, but I do wonder if the entire architecture of the way that Windows programs have been built for decades, the entire Windows ecosystem, would be conducive to what we know as package management. I have to think that the answer would be "yes" and that there'd be a clear vision here before MSFT would greenlight a project like this (the WinGet roadmap does indeed mention dependency support of some description).
I was actually pretty excited to dive in and start contributing to an WinGet, an open-source project, after who-knows-how-many years talking about doing that (even if it's just contributing "package" manifests at first)... but the above comment seems to raise a perfectly good question. I mean, it sounds pretentious as hell to suggest that a Microsoft project isn't worth my time, but I can't help but wonder about the long-term vision here. What does genuinely useful package management even look like in the Windows world? Maybe somebody with extensive experience with Chocolatey et. al. can chime in here.
Yep! They just added their own package manager winget. Imo this all seems to be in preparation for a new version of windows. But releasing all the features early to the people who want them is nice.
... YET!
Please note 1. That this is the first public preview of a brand new Package Manager - there's still a long way to go until its "done" 2. winget is open-source and the team welcomes feedback in the repo: https://github.com/microsoft/winget-cli
Remember a year ago when everyone was wondering why Microsoft was shipping a new command-line Terminal? Nobody has asked that question in the last 5 months.