ASP.NET
Dangers of the new ASP.NET MVC framework
I’ve been following the new ASP.NET MVC framework quite close lately because it looks so damn cool. Not only does it make your website testable in a much richer way, but it also adds abstraction between your different UI tiers. It can do these things because it uses a somewhat strict code separation principle like all MVC frameworks do.
So instead of just adding an .aspx page (with its code-behind file auto-inserted by Visual Studio) to your website, the MVC framework wants you to add a model and a controller as well. The .aspx along with the model and controller is highly abstracted so you can replace one of them easily without changing the others. We know this from the class libraries and components we’ve build for many years – something called low coupling.