51–60 of 122 posts
- "It takes ~3 seconds for WSL2 to start up the first time"
- "Windows Terminal [gasp] has animations"
- "The new spotlight search isn't already flawless"
- "File explorer right-click menus have... too many things in them"
(Paraphrasing, of course)
And I honestly wonder if the flickering thing is a problem with the author's GPU or something. Seems to happen everywhere and I've never seen it on my machine.
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…
They already admitted that they were wrong about Open Source and even though there is room for improvement, I'm happy that they are supporting power users more and more.
Earlier quoted context omitted.
Basic Features in separate packages means, many users will never use them, because they don't know they exist. Bulk renaming files for example is not something only power users do, it is something only power users can do because it just does not exist and/or is not discoverable for a normal user. And also as a power user, it is annoying to find a program for every basic thing the system should be able to do. On the o…
> Basic Features in separate packages means, many users will never use them, because they don't know they exist. If people want/need to do something such as bulk renaming, they can online search for it, as they do for everything else, which will tell them they can install a package from the windows store. Doesn’t seem that crazy to me as an expectation from end users. Also, I don’t think that when Microsoft says “pow…
Or they'll find some sketchy exe file, and here comes the malware! Windows is really broken in terms of package distribution, and requiring people to go online and search for something so simple is hassle, dangerous, and decreases discoverability for software that really ought to be included in a vanilla install (unlike Cortana, which is a massively bloated feature that many people don't want, but can't get rid of, sort of like Bixby).
Earlier quoted context omitted.
Basic Features in separate packages means, many users will never use them, because they don't know they exist. Bulk renaming files for example is not something only power users do, it is something only power users can do because it just does not exist and/or is not discoverable for a normal user. And also as a power user, it is annoying to find a program for every basic thing the system should be able to do. On the o…
> Basic Features in separate packages means, many users will never use them, because they don't know they exist. If people want/need to do something such as bulk renaming, they can online search for it, as they do for everything else, which will tell them they can install a package from the windows store. Doesn’t seem that crazy to me as an expectation from end users. Also, I don’t think that when Microsoft says “pow…
And even the few who would do a search would probably stop at the scary though of "installing" something.
As a technical person, these are regular observations from my parents or non-technical work colleagues.
We are 30+ years and Windows Task Scheduler is still broken. Compare that to simple .txt files to schedule anything you need in Linux. Windows took the UI path for users and that's OK, but most of Power users are still much better off with text files and simple utilities (like crontab) that work. This type of ecosystem is completely broken on Windows, I don't think it can be fixed, it is too much of a paradigm shift.…
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.
> But the first launch of the Linux subsystem after system reboot is unbelievably slow. Proceeds to provide a video showing a 3s startup time to illustrate the unbelievable slowness that happens once after a reboot. I suspect the favorite activity of the author is therefore to reboot their computer, and to quickly rush to WSL2 after that. In which case I agree the user experience is not ideal.
Continuing to read: > Why is it animated? Or, even if it is, why is animation so slow? Given it is not animated on my computer, I suspect it is animated when Windows is configured to have animations... (and it if this theory is good, it is nice that they respect the disabling of animations, by the way, in contrast with the... Start Menu!)
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…
I switched from WSL2 back to WSL1 because the git action times on the NTFS shared drive were _minutes_ long in WSL2. I didn't use WSL2 for too long and so I wonder: are processes in WSL2 manageable by Task Manager and Windows Defender as in WSL1? That integration with Windows tooling made WSL1 killer for deploying tools to non-programmers; give them a powershell script and they can run the app and manage it in a fami…
I haven't tried (just installed Windows 10 v1909 last night) but I don't think so, given that WSL2 sits in a VM, which WSL1 didn't.
I liked WSL1, but it had a lot of the same drawbacks that Cygwin had, which was that Windows and Linux are different enough under the hood that you start running into issues with file system performance and containers, and WSL2 fixes that at the cost of being clumsier with file management.
The solution I recall for WSL2 is to put the shared files inside the Linux instance instead of putting it in NTFS.
Earlier quoted context omitted.
I’m not sure why it’s important for features to be in the base install (so not in a separate package). Having theM packaged separately makes it easier to push updates, and you only install the power tools if you care about them. That’s quite nice IMHO.
Basic Features in separate packages means, many users will never use them, because they don't know they exist. Bulk renaming files for example is not something only power users do, it is something only power users can do because it just does not exist and/or is not discoverable for a normal user. And also as a power user, it is annoying to find a program for every basic thing the system should be able to do. On the o…