The biggest issue with ASP.NET for me is that it ignores the underlying protocol. The writer tries explaining this away, saying that you can get at the raw htt

The biggest issue with ASP.NET for me is that it ignores the underlying protocol. The writer tries explaining this away, saying that you can get at the raw http components if you want, but I don't think that matters much when the default use of ASP.NET is via the web forms model. Once you're in web forms, you have to pretend like you're not on the web at all. I cannot apply all the knowledge I've learned from perl, php, java(jsp/servlet), and ruby on rails. Basically, it's just not very easy to transfer knowledge of the web over to the ASP.NET framework. You have to relearn how to do basic tasks, and do it the microsoft way.