05/03/2010 10:40:29 AM EST
The hadoopdotnet project does not even have anything in its source repository. It should not even be mentioned in the article.
United StatesEric Hauser
05/03/2010 03:07:27 PM EST
Once you've invested in the infrastructure (data centers, automated provisioning, bandwidth, etc., etc.) you need to drive volume. Microsoft has made the investment and wants to drive volume. They will support technologies that attract users and are supportable and scalable. Microsoft also serves developers - they aren't fighting PHP because it isn't .NET, but want to make Azure a great stack for hosting php apps. They want to do the same with Java and Hadoop apps. Since .NET supports IronRuby and IronPython they will continue to make Azure a great environment for these. Part of the plan here is to allow app-devs to build great apps without having to muck around with OS configuration issues. This is in marked difference from Amazon (which is a "cloud colo" if you don't augment it with 3rd party management services) or Google (which is a highly-limited development environment). I giggled a bit about the statement in the article about Velocity's requirement of admin access being a reason why it's not on Azure yet. Here you see the lingering effects of Microsoft's internal divisions duking it out for control and resources. There has always been a "Windows forever and everywhere" camp slowing down the groups that want to be the best platform for apps. Recently, Office itself has started to wean itself from a requirement to own Windows. I don't think it's a response to Linux as much as a response to emerging access devices (phones, tablets, etc.) and a shift to SaaS/Cloud. Whatever the cause, Microsoft seems fully-engaged in making their cloud-based development platform the richest and easiest to use. Nothing like competition to spur innovation!
United StatesDoug Stein
