I love PowerShell dearly, and I miss it on Unix systems, but what this is trying to fix, and what still stinks at the moment, is the command-line editing situation in Console, which has nothing to do with PowerShell v. Bash v. cmd.exe.

as a .NET developer who sits in both Linux and Microsoft worlds, but primarily in Microsoft technologies, I must say that PowerShell is a very useful and amazing addition to Windows. I did have to learn it, but once I did, I love it.

Yet another tool to learn.

It is definitely worth it for some people, but time is a limited resource, and others will benefit from this kind of project.

starts too slow.

on my PC it is instantaneous, it is a matter of hardware.

No, it's not. I have a TI6x laptop, 4gb of RAM, plenty o' CPU and with no other user-space programs running, it still takes FOREVER to start. I feel like i'm launching Eclipse or something.

Try it on a T410, i7 with 8GB of RAM and a SSD, it takes 2s to start.

it's a SHELL for God's sake! I shouldn't need 8GB and SSD!!!

it is not a matter of hardware. On my ex-work desktop (2.8GHz quad core, so fairly quick) it used to take a good 5-10 seconds to be ready from a cold start. Yes, subsequent starts were faster, but it's a flipping shell, it shouldn't need hefty hardware to start quickly!

Absolutely. Even on my work machine (2.2GhZ, 4GB RAM) it loads within a second.

Yeah, I can also handily disagree with this. My test machine has a 6 month old CPU and 6GB of RAM. I can reboot, wait 5 minutes and try to launch PowerShell and still be looking at a 5-15 second wait.

I have the same problem.