webforms vs monorail
It was bound to happen sooner or later, someone comparing webforms to monorail. All of the pro's and con's make sense and from a webforms point of view it's cons like viewstate and pros like controls/vs support that stand out. For me monorails design is very important in that it follows MVC and you get an ideal world of a clean, light weight view and testability for controller and model. Anyone that has ever tried to unit test webforms will know it's a world of pain. Thats not to say you can't do patterns in webforms, MVP can be done (and Phil Hackk has a great example) but it does introduce complexities that may but folk off. In an ideal world
- webforms would have MVC baked in
- would support templates for light weight view genertion
- would bake in Atlas for templates to avoid page postbacks