Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Implementation details. To the person using the products, they are nearly identical, with one being for web sites and one being for APIs. I see no reason why these should be separate. Please explain.


ASP.NET MVC is approx. 3 years old product and to support the features of the current ASP.NET Web API in an elegant way, lots of breaking changes would occur in ASP.NET MVC. This is just one of the reasons. You might also see this one as another impl. detail but it is the brutal truth.

Gleen Block has a 20 minutes long video on this topic if you need more info: http://www.tugberkugurlu.com/archive/why-do-i-need-asp-net-w...


What features? The difference between MVC and Web API, to those using it, is that Web API uses restful routing and MVC does not. That is all.


It's pretty impressive to see people who have no idea about the technology they are talking about. ASP.NET Web API doesn't force REST at all! Go learn what that FX does in the first place before leaving comments like this.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: