[giu]

Perfect timing. After having used Linux full-time in private and at work for the past 13 years, I had to switch to Windows 10 at my new job. I miss the hell out of my shell, my .zshrc file, and the general "easy" customization of Linux, but I'll be more than happy to see how I'll better adapt to Windows 10 thanks to this list and the tools provided in the comments here.

Edit: First thing I'll install is most probably the Windows Subsystem for Linux :)

[netfortius]

... took the cygwin path, instead, in a similar situation (company imposed Win10 laptop), albeit my macbook w/macos + homebrew is still the best combo, which I am also trying to leverage as much as possible for work.

[hans1729]

was about to ask "how are you not running wsl yet" :) if you have any questions, hmu, I switched deliberately to windows 10 from macos on my worklaptop, because wsl + vscode is evil black magic

[dragonwriter]

WSL is good for for running Linux on top of Windows with convenient but not always efficient interop, but if you just want Zshell for Windows, you can do that too:

https://medium.com/@borekb/zsh-via-msys2-on-windows-3964a943...

[agustif]

You might want to checkout the new Windows Terminal app too for it.

You can basically keep your unix/zsh env for windows, I even make aliases for things like open = explorer.exe, ls = dir, etc...

[etlandis]

A nice chunk of unix tools get installed with git (if you select the option to) - you could just add it to your path and it saves on a fair chunk of that aliasing work

I think my biggest annoyance with powershell in particular is that curl is aliased into this awkward powershell function by default

[jodrellblank]

> "I think my biggest annoyance with powershell in particular is that curl is aliased into this awkward powershell function by default"

Not since August 2016 and the release of PowerShell Core 6. "PowerShell" now refers to the cross-platform branch, currently PowerShell 7.1.

The older one with that alias is now "Windows PowerShell", and is legacy and no longer developed.

[dragonwriter]

> The older one with that alias is now "Windows PowerShell", and is legacy and no longer developed.

It's still distributed by default with all versions of Windows where it is labelled “Powershell” with no qualifier.

Microsoft’s branding isn’t particularly internally consistent, so being ultrapedantic about one particular presentation of it, and one that itself conflicts with the one pushed most immediately in front of the largest set of customers by Microsoft, isn't necessarily a great approach.

[jodrellblank]

> "It's still distributed by default with all versions of Windows where it is labelled “Powershell” with no qualifier."

No, it's called "Windows PowerShell", look: https://i.imgur.com/119yPbK.png

> "so being ultrapedantic about one particular presentation of it, isn't necessarily a great approach."

https://docs.microsoft.com/en-us/powershell/ - official documentation has sections for "PowerShell" and "Windows PowerShell 5.1".

You have outdated information. You can either update your information and use the current names, or you can pretend a tool from 4 years ago which has been deprecated and superceded at least twice, is the current one, the same way you can pretend that Windows 8 is the current desktop and be angry about the full screen start menu that "Windows has".