2 ms·
You can type / and it works in Powershell. I've been using Unix for 20 years, switch to pwsh 2 years ago, never typed backslash ever.
by nailer 8y ago
You can type / and it works in Powershell.
I've been using Unix for 20 years, switch to pwsh 2 years ago, never typed backslash ever.
- 10eleven 8y agoWHAT
- 10eleven 8y agoThis changes everything
- eBombzor 8y agoPowershell is considerably slower than cmd. Does that not bother you?
- majkinetor 8y agoIt starts under 1s without modules. That is enough fast and still infinitely distant feature-wise of cmd.exe. You can make it go over 1m+ if you have a lot of modules to load, particularly with method of writing modules where you put functions into separate files (and no SSD) and/or some specific cmdlets in the profile. It can even be worst then that in particular environment - for instance within VSCode some of my scripts can take several minutes loading (while being otherwise instant). In other words, you can balance your environment for speed vs features. I believe Pwsh will get considerably faster in the future given that optimizing it will pay out on nano server which currently boots faster then PowerShell is loaded in it afterwards (which rly sux).
- nailer 8y agoIt takes 1600ms to open a tab with my full large profile. Yes that's annoying. bash requires scraping everything and is inherently brittle as a result, which has always bothered me much more.