Microsoft has announced it will release the source code for ASP.NET Web API and ASP.NET Web Pages, and will also invite third-party developers to contribute code to the products. The news was slipped out in a blog post by Scott Guthrie, a Corporate Vice President in the Microsoft Server and Tools Business. The post says the …
But who gets the most out of this ?
Now, before this comment is picked up as being solely cynical or negative... No, I applaud this development because IMO this is a step in the right direction. After all; at the very least do we get a little more insight in the software which Microsoft has provided us with in the last few years which I think is good.
Another reason why I consider this a good development is because its a somewhat logical step. I mean; their development environments (talking about their Visual Studio 2010 for Web development here) have been available in a free ('Express') form for quite some time now. So if you want to get your hands on the ASP Web API you could. Simple. As such its IMO only logical to open things up a little more. And who knows what might follow ?
However, I do have to wonder if MS doesn't get the better end of the deal here (of course they do this for a reason of their own as well, sure).
You can pick up the source code to the Web API (which is basically a framework) but then what? While you can pick up an ASP 'container' (IIS) for free as well, it doesn't give you the amount of freedom you'd have if you could also get access to the source code of the underlying engine. So then I start to wonder how others may benefit from this, also considering that this is basically a framework build on top of ASP.NET which remains closed.
I know about stuff such as mod_mono or Apache::ASP but even then I have some doubts if this API will / could be beneficial there. Because that is IMO one of the boons of open source; the ability to pick something up and utilize it in totally different ways. Yet I don't think that will really apply here (though I could be wrong of course).
So; not to sound ungrateful or anything. IMO this is an admirable step in the right direction, I think we can all benefit in the end with a more transparent Microsoft, but in this case I do have some doubts.
Re: But who gets the most out of this ?
For some reason I now have an obscure Rolling Stones song called 'Dirty Work' going around in my head.
Re: But who gets the most out of this ?
Maybe - just maybe - us.
MS has licensed this stuff under APL2.0 - which includes an explicit patent grant.
Now I don't know enough about ASP and its various components to know how deep this goes - but has MS just cleared up some of the patent uncertainty?
Past experience tells us to be extremely cautious dealing with MS "gifts" - but I'm actually quite encouraged by this.
HTML5 is a proper standard and starts to edge out Flash - Adobe make Flex open source
PHP has become the de facto standard over ASP - Microsoft make ASP open source.
Seems like both projects are good at what they do, but people are moving away from them *, so pushing the source out to the community is worth a try - gains the company FOSS brownie points and may even help fight back against a more popular rival. I feel ASP is the IE6 of server-side scripting.
* based on no research at all, but certainly getting a LAMP host is cheaper and easier than a Windows one, and the advertising industry has helped infect Flash as well as iOS restrictions.
This is ASP.NET not ASP.
ASP is legacy interpreted script similar in function and features to PHP.
ASP.NET is compiled server pages built around the .NET framework.
I think it is very good that MS are making this open-source should increase feature set, and reduce turnaround time on bugs and issues.
*sometimes it is better to research.
"ASP is legacy interpreted script similar in function and features to PHP.
ASP.NET is compiled server pages..."
Well, PHP is also compiled. It's debatable whether the .NET library makes ASP.NET superior to PHP.
"I think it is very good that MS are making this open-source should increase feature set, and reduce turnaround time on bugs and issues."
Patches aren't applied willy-nilly. Just because someone submits a patch, doesn't meant that it will be accepted.
Microsoft is making Stuff Open Source? This must be the actual end of the world being near then...
- The land of Milk and Sammy: Free music app touted by Samsung
- The long war on 'DRAM price fixing' is over: Claim YOUR spoils now (It's worth a few beers)
- Privacy warriors lob sueball at Facebook buyout of WhatsApp
- 20 Freescale staff on vanished Malaysia Airlines flight MH370
- Dell thuds down low-cost lap workstation for
cheapfrugal creatives or engineers