25 May 16 11:48, you wrote to me:

 ac>> There's nothing stopping anyone running a WAMP stack under Windows
 ac>> 10 right now though. So I don't think that's the reason. Well not
 ac>> unless they wanted to be petty. It wouldn't be the first time.

 TL> True regarding the WAMP stack, though you don't have all the other GNU
 TL> stuff with WAMP. :)

Yeah, which goes back to what I said earlier.

 ac>> You're right about the risk Microsoft is taking potentially losing
 ac>> customers (web developers spring to mind) once they become
 ac>> accustomed to the Linux command-line. Not necessarily losing them
 ac>> to Linux either, but to OS X. But I'm sure they've considered that.

 TL> I'm sure they have factored that in.  Microsoft have been around a while
 TL> now.

Definitely, but it's a different culture there now. The markets they've been
historically involved in have become very fragmented.

 ac>> I'm curious what their plans are for Windows Server now that
 ac>> Windows 10 is essentially a "rolling release".

 TL> Good question.  I can't see Windows Server going rolling release,
 TL> they're more likely to offer hosted solutions for smaller business, I
 TL> suspect.  Larger enterprises will still want to have their degree of
 TL> control.

I think so too. But consider that Windows Server and Windows 10 share a lot of
code, the temptation for Microsoft might be to release a new version of Server
more regularly than we've seen in the past, just so that Windows 10's features
don't get too far ahead of Server's.

OTOH I'm not sure what features they can add to Windows Server until they run
out of ideas (or marketable ideas, anyway). Linux binary support is a good one.
And now this message is on-topic for this echo. Huzzah.

--- GoldED+/BSD 1.1.5-b20160201