3 ms·
I did the same around 2 years ago after 15+ years of Linux Desktop as primary OS but I had completely different experience and have not gone back to Linux and s
by ComradePhil 5y ago
I did the same around 2 years ago after 15+ years of Linux Desktop as primary OS but I had completely different experience and have not gone back to Linux and see little reason to do so.
> when you install a Linux distribution, it’ll start off either all KDE or all GTK,
Yes, you definitely start off with that... and you may even be able to maintain that with GTK to some extent... but if you want to use KDE, you will most definitely end up with a few GTK apps which will look out of place. And don't even get me started with other DEs.
Windows, with all the 10 vs 11 and old style vs new style apps, feels much more coherent.
> You can’t customize anything
You don't need to because things actually work.
> I am a software & web developer - and Linux is a toolbox, full of highly polished tools, crafted over decades by software developers, for software developers.
Huh? I do all my development on Windows + WSL2 and run all my software on Linux servers. There is exactly ZERO tools I miss.
> Non-composable Software
Absolute nonsense. Not only does PowerShell is extremely powerful, you can also pipe output from a PowerShell command to a Linux command. The following shows an example of grepping through PowerShell history.
cat (Get-PSReadlineOption).HistorySavePath | wsl grep "ssh .*ubuntu@"
> Environment Variables look like this: %PROFILE%, instead of this: $HOME; which is fine, just different; although PowerShell seems to accept either form, which is nice.
Unless you want to run legacy batch files, there is absolutely no reason to use legacy cmd.exe over PowerShell on a Windows terminal. Environment variables are accessed differently with $Env:VAR_NAME, which will take some getting used to, but it's fine.
> No Middle-Click Paste
There are 3rd party applications to do that and more.
- majkinetor 5y ago> You don't need to because things actually work. Customization is not about things working but about user experience. > There is exactly ZERO tools I miss. Yeah, because even if you do, WLS or not, you can have them on Windows in single line: cinst curl wget less jq vim grep gnupg whatever > Non-composable Software Not only PowerShell which is amazing but you had few more different composing technologies all the time such as COM.
- NotTheDr01ds 5y ago> you can also pipe output from a PowerShell command to a Linux command. Agreed - PowerShell <-> WSL integration is pretty nice. Just remember (mostly for others reading) that PowerShell has a nasty habit of automatically appending a trailing newline when piping to external commands like WSL. So you often need a "tr -d '\n'" in the WSL part of your pipeline.
- tored 5y agoPowerShell also has a weird default encoding when piping.