A list of problems I have experienced in my first week of using PowerShell extensively:

- Scripts won't run unless they are signed. Documentation does not provide a workable solution. ("Unblock" button is not present in script file properties)

- No apparent way to do reverse history lookup (like Ctrl-R in most Bash shells). You have to retype the whole command again with the rudimentary autocompletion, unless you can get scripts to work...

- Seems to have lots of support for .NET environment, but none of this is useful for other languages such as Java.

- EDIT has been removed in Windows 7 (and Vista I believe) - No replacement out-of-the-box text editor? This is vital for systems with security preventing installation of alternatives.

- You either have tabs or inline command shell. The ISE wrapper separates STDIN/STDOUT into separate windows. No apparent way to get a proper inline command shell with tabs?

- No pipelines (anonymous or named), IPC is limited to the in-built capabilities of the programs used. Cygwin only works for Unix tools ported to the platform.