Comment by sixbrx
11 years ago
That's the main thing I would be interested in also, but I'm thinking that's one thing that we WILL NOT see. That could seriously undercut the need to buy Windows servers.
11 years ago
That's the main thing I would be interested in also, but I'm thinking that's one thing that we WILL NOT see. That could seriously undercut the need to buy Windows servers.
"Devices & services" Azure is your servers and the .net + C# tooling story from dev to deploy makes the question of selling Windows servers in a VM world moot. Many of the moves coming out of this Build seem to point to a world where it's going to be cheaper and easier to pay for all the MS services and tooling than to try to cobble it together with other people and platforms.
We're looking at a lowered on-ramp to .net apps that run more smoothly than java+linux+every-support-tool-bit (dev-wise) across devices (and things). It's compelling.
Everything from dev to deployment and ops is getting touched at this conf. This shows where MS's strengths can present differentiation. Their profit source is, and has been, building/selling tools and platforms for others to run businesses. When the thing people hate becomes more like what they aspire to have/be, the tension is palpable.
Google is about the only other player nearly capable. But Google's mission has far less to do with selling shovels vs. harvesting and monetizing.
Apple is just not in this space. If anything, they sure feel like a device-only company in this conversation. WWDC is about the garden. Build is handing out spades, shovels, and, now, dirt.
Xamarin's Evolve, last year, felt a bit like all this does. The are big things happening. If nothing else, at least it feels like change, if not progress for devs and consumers.
There's a trade off though. If C# only runs on Windows then a lot of developers who run Linux will never consider C# as an option. If it does run on Linux, then those developers might end up purchasing Visual Studio in order to develop C#. A lot of developers who previously used C# are also leaving the tech for others like Ruby since they aren't tied to Windows.
Yeah. Historically at least, the Mono runtime was one of the weak points when running C# code on Linux and I expect it drove a fair few Windows sales - you could develop applications under Linux but if you wanted them to run well you needed to pay out for Windows licenses. (I believe it's improved a fair amount over the years but is still behind.)
The .NET VM would be pretty much useless on other platforms. It is tied to Windows and it would be pretty hard to rewrite. But standard libraries would be different story.
I think it would be a long way from useless.
The garbage collector for example would be very interesting to peruse. Sure threading and synchronization code would be differ but these have been emulated on Linux before to good effect, I don't see any serious barriers there.
Microsoft has released the source for a .Net VM (CLR) in the past: http://en.wikipedia.org/wiki/Shared_Source_Common_Language_I... It supported FreeBSD and MacOS X. This suggests it would not be impossible for them to make a multiplatform .NET in the future.
A significant subset of .NET had to exist anyway for Silverlight to run on the Mac.
I'm sure the codebase is factored internally to have some sort of platform abstraction.