<story><title>Mark Russinovich, Microsoft Critic, Is Now Building Azure</title><url>http://www.wired.com/2014/05/mark-russinovich/</url></story><parent_chain><item><author>Touche</author><text>&amp;gt; “I ranted at some of the architects when I was at Microsoft. They were constraining the sorts of things you could do,” Brown told us in 2012. “Microsoft likes to do a really big up-front design, where they define the physics of a new universe. They birth this new universe, and they say: ‘This is how you do it’–instead of starting out with something simple and letting people show them how it should be done.”&lt;p&gt;I really hope this advice is taken by others, particularly the Windows team. Powershell is a golden example of this. Great idea, piping around objects instead of text, but wait, they must be .NET objects. So the entirety of the language community cannot participate other than Microsoft languages.&lt;p&gt;I&amp;#x27;m hoping they revitalize the command line taking this advice, start with something simple and let others build on top of it.</text></item></parent_chain><comment><author>MattRogish</author><text>Absolutely.&lt;p&gt;MS is full of architecture astronauts (along with super smart people, who do useful things - but the arch people are in charge) that sit around and contemplate all these bizarre use cases for things that no one actually has. Then, since MSFT believes they have little&amp;#x2F;no competition in the space, they spend years developing this grand vision and dumping it on their customers, who then attempt to figure out what parts of this vision are useful and what parts are bunk.&lt;p&gt;Microsoft then looks at what happens, sees the work arounds, and rewrites the whole thing again to accommodate not only those use cases, but a whole host of other imagined ones, too.&lt;p&gt;Lather, rinse, repeat.&lt;p&gt;Open source generally doesn&amp;#x27;t have this problem, as a) some developer was scratching their own itch, so the problem is real b) doesn&amp;#x27;t have unlimited time and budget, so they have to keep it small and evolve, and c) relies on developer&amp;#x27;s contributions, so it has to be marketable.&lt;p&gt;Open source : Microsoft :: Lean startup : Waterfall</text></comment>
<story><title>Mark Russinovich, Microsoft Critic, Is Now Building Azure</title><url>http://www.wired.com/2014/05/mark-russinovich/</url></story><parent_chain><item><author>Touche</author><text>&amp;gt; “I ranted at some of the architects when I was at Microsoft. They were constraining the sorts of things you could do,” Brown told us in 2012. “Microsoft likes to do a really big up-front design, where they define the physics of a new universe. They birth this new universe, and they say: ‘This is how you do it’–instead of starting out with something simple and letting people show them how it should be done.”&lt;p&gt;I really hope this advice is taken by others, particularly the Windows team. Powershell is a golden example of this. Great idea, piping around objects instead of text, but wait, they must be .NET objects. So the entirety of the language community cannot participate other than Microsoft languages.&lt;p&gt;I&amp;#x27;m hoping they revitalize the command line taking this advice, start with something simple and let others build on top of it.</text></item></parent_chain><comment><author>ygra</author><text>PowerShell also plays nicely with COM and WMI. It&amp;#x27;s not all .NET objects you interact with. (Well, technically it is, due to PSObjects wrapping everything, but that&amp;#x27;s another matter.)&lt;p&gt;How would you do it, though? Pipe around JSON or XML? Then you just have data structures, but not objects. They can&amp;#x27;t have methods and if they could, what language would they be written in?</text></comment>