81–90 of 122 posts
Putting ads in your 3 second blog animations? Really? Comes across as incredibly trashy. Unrelated to the article, sorry. I have never seen this before...
I tried WSL2 for about six months. I'm really glad that MS is investing in this and it's an aspect that has been long neglected. If you're a developer, and unless you're using MS stack (.NET), the experience has been always subpar. I have to agree with the author that the experience is not quite there yet. But a lot of progress has been done. And I hope the progress continues and maybe in the future I'll try it again…
People all over the comments accusing me of nitpicking. I can agree with that. But I also feel like this happens because of what you call "a thousand paper cuts". It works, but feels surprisingly unpleasant.
Allowing us to run Unix command line in Windows is a great achievement for Windows team, props to them. But it isn't yet comparable to the real deal like Linux or OSX. The speed, the looks, the integration. I'm actually surprised that (subjectively) Linux UI with all that fragmentation looks a bit more consistent than one of Windows.
I hope Microsoft addresses all these problems, but guessing from previous experience it make take a while.
Can windows terminal be used remotely? The only remote terminal I am aware of in windows is remote powershell but it sucks badly. It takes ages to come online after a reboot, is unencrypted by default, and because of security issues cannot interact with windows update.
Yes, you can do that with ssh even from cmd.exe. Windows ships with an ssh server too, you just have to enable those features.
This seems like a joke article. The 'long' startup time appears to be a second or two. The slow animated menu is quick - I'd like to see someone actually select a menu item in the time it takes for it to drop down. The animation doesn't impact usability. All a bit bizarre.
Good to know. But sad that I had to look in the comments for this information, because for some reason the video doesn't play. I'm not sure how the article author thought it'd be a good idea to embed a video containing the same amount of information as a single number, but I guess that's considered a feature in the modern web.
Earlier quoted context omitted.
It is not weird at all once you realise who Microsoft's management wants as its customers. The business people at MS really do not expect nor want customers to be fiddling around with technical stuff. They want customers to see MS as the one who can solve all problems. The business people at Microsoft prefer non-technical customers. Technically-minded customers are not the ideal customers for Microsoft. A great examp…
Nonsense. Different products (from MS) are for different people. If it was true what you are telling, doubt they woild provide loads of diagnostic tools for windows, debugging tools, kernel symbols, performance tools, etc.
Comparing the most important product(s) at MS with any other MS product/project and arguing they are somehow "equal" in the eyes of MS (because press releases, marketing) is a losing game.
Why is this blog post so negative? Microsoft are trying and giving all of the developers the tools to help affect the project along the way. The Terminal project was only announced 1 year ago[0]. As I understand it, they had to more or less split how the whole conhost.exe work in order to allow Terminal to even exist. The settings UI is far from sexy, but they're working on it[1]. I think it's impressive to know that…
(Also yes, it is unintuitive that you may want to install VSCode first in order to edit Windows Terminal settings, but is it that much of a stretch that Microsoft would imagine early adopter power users to have VSCode lying around already on their machines? As you said, they are working on a "proper" UI for Settings still, but as a first "get it out the door MVP release", especially with all the under the hood work that took to get them there, it still seems a reasonable play.)
I actually don't get Powertoys at all. They provide basic functionality I would not even class as for power users. Yeah, they are nice, they were nice in win95. Why do I need a separate Program 25 years later to rebind some keys or switch windows, yet every new win10 version tinkers with cortana? People say it would add "bloat", but somehow basic functionality beneficial to many users is bloat while candy crush and x…
I can't find it now, but I've heard the PowerToys developers talk about how the long-term goal is to move some of these features into Windows.
It's useful to have a laboratory to test things with less impact if the experiments fail.
The history of Microsoft is the history of workarounds on top of workarounds, year after year, rinse and repeat. Here's a novel thought: instead of providing yet another iteration of workarounds for the power user, how about just fixing it for every user. Take for instance the Start Menu. When the Win-X "quick access" menu was added years ago, it was essentially an admission that the Start Menu is not the best way to…
One of those "context" switches that Microsoft finds is a useful context to know is "power user" versus "regular user": regular user Start Menu versus power user Win+X, regular user Search and Run versus power user Win+R/PowerTopys Run. (At one point in Windows 8 Microsoft tried to use the Win+R shortcut for something that wasn't "power user run a thing" and nearly saw a revolt.) It becomes a self-selecting "reveal" of different feature sets to match what features the user thinks they are ready for.
I tried WSL2 for about six months. I'm really glad that MS is investing in this and it's an aspect that has been long neglected. If you're a developer, and unless you're using MS stack (.NET), the experience has been always subpar. I have to agree with the author that the experience is not quite there yet. But a lot of progress has been done. And I hope the progress continues and maybe in the future I'll try it again…
It's an interesting tangent, but Insider Preview updates are fascinating from a technical standpoint. Nearly every single one is installed closer to how Windows' big "Feature Updates" work (as essentially full Windows images that get built to a new folder, all the old things installed back into it, then the old Windows folder archived or removed) than old school sets of patches to individual files. It's been interesting as an Insider since very early in Windows 10's life to see how much faster these updates have gotten over time. Installing lots of updates this way on Insider Preview machines seems to have helped a lot make the big "Feature Updates" themselves faster/better/more reliable. It's maybe not as obvious to someone installing a big Feature Update at most twice a year, but as a long time Windows user and having seen the gradient of change in Insiders Preview (and read some of what I could in their discussions on the technical efforts on blogs), it has been fascinating to watch.
WSL2 should be out of preview in the soon-to-be-rolled-out May 2020 feature update.
Earlier quoted context omitted.
Can't bulk-kill processes, for one. Not searchable, for two.
Haven't used it in a long time, but looking at it now, the GUI is definitely clunky and those features are missing. Wasn't there another GUI during the Windows XP days?