This is terrible. And there are lots of reasons why if you sit down and read the comments you’ll find lots of reasons why, but here is my number one reason.

  • PowerShell = PS = 204,000,000 irrelevant hits on Google.

Monad obviously had issues with leading character substitution but at least it was largely searchable. MSH wasn’t two bad, but it is also a segment from a HL7 formatted message which made it near useless for searches.

This is a call to arms, bloggers unite and let Microsoft know that they need to go back to the drawing board on this one.

4 Responses to “Please don’t make “Windows PowerShell” the official codename for Monad.”


  1. I notice on SlashDot that they’re already starting to call it “Windows Powers Hell” … :\

    I dunno … what would you prefer? “Windows Command-Line Foundation”? :) At least it’s a kind-of marketable name compared to some of the monstrosities they’ve come out with lately.

  2. Mitch Denny Says:

    Sometimes I don’t know why they don’t just stick with codenames :)

  3. Josh Says:

    I’m not sure that you can argue that the term PS returns useless search results. That’s an acronym – just search for PowerShell. It’s a bit like arguing that WV returns a load of nonsense when you’re searching for windows vista :)

    I bet the think tank peeps are kicking themselves about the Windows Powers Hell though – joy!


  4. I totally agree – PowerShell is a stupid name – monad / msh was much better.


Leave a Reply