It will get shot down due to legacy requirements. It boggles my mind they didn't start Powershell "legacy-free" and just emulate/re-implement the existing command line commands.

The problem if you do that, as soon as you run a console EXE, you're hosed, weird things will happen.

As any of us who run resource kit, support kit, or development kit tools have found ;)

Thanks for your unofficial input throughout the threads. They've been great nuggets of info and insight from the inside, so to speak.

Thanks - I certainly don't believe that Microsoft always has a good reason for what they do, but I try when I can to illustrate what was going through the engineers' heads when they built the thing.

When you build a system that has to work for everybody, from your grandma who just wants simplicity, all the way to the Federal Gov't who has complex requirements and restrictions, all while making 100% sure that everyone's programs work flawlessly even if they happen to be horribly written, sometimes you have to make lousy compromise choices, I think that's our biggest challenge by-far, is balancing the n-degrees of concerns through smart, disciplined engineering.

Also, here's a great example of how we have to balance "fix the bug!" with "make programs work!":

http://blog.paulbetts.org/index.php/2010/07/20/the-case-of-t...