Yes, it's great that Exchange can be scripted (and I've written some neat ones), but the Powershell long-winded command names is highly annoying and basically require an IDE to anything beyond the most cursory scripts. Meanwhile, I can code Bash scripts a lot more quickly.
I'll be blunt. After coding in Powershell for a couple of years now, and appreciating how, since Server 2008, Microsoft has opened up a lot of its core functionality in its various server products to scripting (although, oddly enough, I still can't dump Exchange 2010 public folders to a PST file like I can mailboxes), I still come to the conclusion that Microsoft just doesn't get CLIs and CLI scripting. Powershell opens up a lot of options, but is absurdly long winded about it. Bash is still a superior CLI shell.