views:

422

answers:

10

This question is only looking for feedback on the direction of ASP.NET MVC as a platform. I truly am not posting it as flame-bait. My company is planning a major web application investment and we need to decide if ASP.NET MVC is the right direction.

===

Update Microsoft Answers

Scott Guthrie, head of ASP.NET development, posted this on his blog:

ASP.NET MVC is a free, fully supported, Microsoft product that enables developers to easily build web applications using a model-view-controller pattern

So as long as the above statement is true then ASP.NET MVC is safe to deploy on.

ASP.NET MVC is released under the Microsoft Public License (MS-PL). MS-PL is an OSI-approved open source license. The MS-PL contains no platform restrictions and provides broad rights to modify and redistribute the source code.

===

When Microsoft released ASP.NET MVC under open source (MS-PL) licensing my first thought was that MS might soon drop support for it. And with that thought I wouldn't want to invest in mastering it for obvious reasons.

I could be wrong, so I wanted to get some feedback before making any solid decisions.

Is this a good thing?

Update:

A friend asked a compelling question about this subject: Is ASP.NET MVC Open Source or Shared Source? That got me thinking about the difference between Microsoft's open source-like initiatives and the open source community's "true", if you will, open source. And this difference really gets at the niggling concern over Microsoft open sourcing an important product. It's not that having access to the source is unappreciated. That is GREAT. I wish we had access to Win32 source, or even the entire source code for Windows. Talk about solving problems quickly! The concern is over whether MS will now take a hands -off posture towards ASP.NET MVC. In that case I don't know if we should use it as it could take awhile for robust community support to build around a source collection originally owned by a company not generally known for giving away source code.

+3  A: 

The question you should ask is "Is this a bad thing?" Of course not.

Microsoft's choice to release MVC as open source is an example of their changing views on open source and free software. I extremely doubt they've done this so they could drop support of it.

jfar
+6  A: 

Open source is always a good thing. Now, If MS drops support for it, the community will continue to develop it. Before, if MS had dropped it, it would never be updated.

Zifre
I might be wrong, but AFAIK ASP.NET AJAX is open source as well, and MS has more or less stopped supporting it, but the community behind it does not really take care of this either.
Adrian Grigore
I would say this is because the community has migrated to jQuery, which is used by a larger community, has broader support and has more active development.
Todd Brooks
As for ASP.NET AJAX, I agree with Todd Brooks. It wasn't that MS dropped support for it capriciously, but that the development community has moved to enthusiastically support jQuery.
CLaRGe
I agree with Todd, even microsoft changed the focus on their ajax development based on the adoption of jQuery.
eglasius
That said, I agree with Adrian in the sense that there is no guarantee that work would be continued on it by the community. Specially as MS isn't accepting patches, so you won't have a active community actively/actually working on it.
eglasius
Just to clarify, ASP.NET AJAX is neither dead nor unsupported. In fact, Microsoft will be including a new version (4.0) with Visual Studio 2010, with new features and functionality ... http://msdn.microsoft.com/en-us/magazine/cc972638.aspx and http://www.asp.net/learn/whitepapers/aspnet40/
Grant Wagner
Either way, if Microsoft drops support and leaves it in the hands of the community and the _community_ chooses not to support it either, then was the project worth investing time into? I think community support is very telling in the value of time invested into a project.
Hugoware
Yes, there is no guarantee that the community will continue to develop it, but at least there is the possibility.
Zifre
@Grant I am sure Adrian was referring to the Ajax control toolkit. On the asp.net ajax, I don't have the link but I recall they stating that the idea will be to complement jquery, its a change of focus.
eglasius
+2  A: 

Why on earth would anyone think that open source is a bad thing?

hasen j
Security? A malicious user's work is simplified when working against an open-source code-base.
Andrei Rinea
Corporate management or the legal dept may not approve of using open-source software for many reasons. This is one of the reasons Microsoft has duped popular OSS projects.
Ben Robbins
idiots who don't know how programming works yet happen to manage the industry eh ..!
hasen j
@Andrei, open source usually means better security. More people can see the code and spot bugs.
Zifre
+1  A: 

I would be SHOCKED if MS dropped support for it just because it was open source.

When MS made the announcement that they are shipping jQuery, it went along with a statement that they would start supporting jQuery as a product.

So, if they will be supporting open source products that they don't maintain, I would be shocked if they stopped supporting open source products that they DO maintain.

Brian Genisio
A: 

You can get source for the entire .NET Framework -- I don't think MS will be dropping it anytime soon. I think that open sourcing MVC is reflective of the stance that MS is taking toward being more transparent with their source and cooperative with the open source movement, not that they are expecting to cut it loose soon. Regardless, its a tremendous framework and I fully expect that MVC will continue to support it as it allows them to compete with Ruby/Python/Java in the MVC space.

tvanfosson
Being able to read the source does not mean it is open source.
Zifre
Point taken, but I think that the decision to open source MVC is being made more in the spirit of transparency and sharing that releasing the source to .NET also reflects. That was my point.
tvanfosson
@Zifre : Exactly! It's called shared source and NOT open source
Andrei Rinea
+1  A: 

Microsoft making asp.net MVC open source has no relation with not supporting it. Remember the way it was released as open source, means MS will be the one making the changes along the way. Note that for the moment they won't be accepting submit of patches, which is another clear indication they are in total control of the project.

eglasius
yes but you do have the right to modify the source for your own needs.
Andrew Robinson
A: 

We just last night had an MS Presentation for our local .net users group on MVC. There was discussion about the open source aspect of it. Within 24h of the source release, the Mono folks had adopted MVC. This is all good stuff!

I am hearing tremendous interest within the dev community for MVC. Microsoft seems firmly behind the pattern and framework. I hightly doubt they will be dropping official support for it any time soon.

Andrew Robinson
A: 

it REALLY DOES NOT MATTER even if MS drops support for it. because since its open source, community would continue working on it

thats the power of open source communities - even a software giant like MS was forced to change its views and embrace it. they are doing more and more of open source these days. and its good for all of us (developer community) ;-)

Raj
Using "embrace" and "Microsoft" in the same sentence reminds me of the ominous sequence: "embrace, extend, exterminate"
Piskvor
@Piskvor : I don't get you people; when they ignore it (Open source) they are evil. When they adopt/embrace/wtf_it it's also bad. When is it good?
Andrei Rinea
A: 

It would be worth the time of every project which intends to use MVC to consider if MVC is seriously supported by Microsoft and the community, and what the risks of using MVC are to a project (against the benefits).

Will MVC last for the expected lifespan of the project, once deployed? If the best guess is unsure or no, potentially consider not using MVC.

pearcewg
A: 

Microsoft's commitment to support any product is based on market acceptance, competitive considerations, and product positioning. Their track record is inconsistent no matter whether they open-source it. Think IE and Frontpage. Opening the source code can only increase your chances for stability in the long run, IMHO.

le dorfier