Powershell ties in much, much better to the Windows infrastructure than any POSIX-like shell does. Managing Windows revolves around managing long-running servic

Powershell ties in much, much better to the Windows infrastructure than any POSIX-like shell does. Managing Windows revolves around managing long-running services, and sending off requests to them which return rich data objects. This is an entirely different problem set from managing processes and files. Modifying Windows to be administrable through a POSIX shell would change what Windows fundamentally is. I'm not sure that's a great idea. Personally, I enjoy working with Powershell much more than I enjoy working with Linux in the traditional way (through a shell), and I currently don't personally own a Windows machine. I don't think a shell is a very good interface for direct use; it's entirely non-discoverable past man pages. It's a great interface for developing reusable tools, though. I strongly dislike having to use it directly, preferring to develop scripts that I can access from my text editor. As a developer, I think what you want from a shell is different from what a Windows admin wants from their shell. The Windows admin wants to manage the services they have installed; the developer wants to manage whatever files they have in their source tree. I don't think it's particularly terrible that Windows should be bundled with a tool for administrating Windows, rather than a tool for developing new software.