3 ms·

I think the issue is with Webforms specifically. Webforms abstracts away so much of the way the web works that developers who have spent their careers developin

I think the issue is with Webforms specifically. Webforms abstracts away so much of the way the web works that developers who have spent their careers developing on it never actually understand how the web really works. Concepts like Viewstate hide the realities of web development. The fact that almost all processing takes place on the server-side means they are weak at client-side debugging, etc. That said, I don't think it's fair to hold the same opinion of ASP.NET MVC developers - as it's essentially the same level of abstraction as Rails.

pmarsh 15y ago
Having just spent the past couple of months learning webforms ASP.NET coming from a PHP/RoR background what you said is exactly what frustrated me. Knowing how webforms tried to warp how the web actually works was truly annoying. I understand why they did it, but it really does not help a web programmer in the long run. And if .NET 4.0 didn't allow you to use ClientIDMode to set your own element IDs I'd have lost it entirely.