So ASP.net has become the "toy" framework, replaced by ASP.net MVC, a framework inspired by monorail, which in turn was inspired by rails, the original "toy" framework. Ah, sweet, sweet irony.
Open Source Apps Should Start Innovating - Not Recreating (cli.gs)
also made it to the front page. Charles H. Ferguson has a nice take on this VB/.NET/Java(script)/HTML misery in his book ...not that I agree with him on some issues (like sw patents). But the one who has submitted the original article might know more, since he could have been around there around that time...
How could you want to obscure what are very easy and simple tools still baffles me.
And having talked with some programmers who use nothing but ASP.NET it's amazing how in the dark it has left them.
It's because HTTP/HTML is a very simple tool for what it was created to do: retrieving and displaying static pages.
Everything else is not so simple. As soon as people started to move data entry forms with master detail screens, etc. onto that platform things were getting nasty.
Since Microsoft is the master of master detail forms, or at least of the platform on which most of them have been built, they felt a need to come up with a solution.
And the solution the "company who never understood the web" came up with was ... XMLHTTPRequest. No, seriously, it was ASP.NET. No, wait, it was both! ;-)
The world is confusing.
What had been missing until now, at least in an official capacity, was a way to make serious public facing web apps and I think Microsoft has made great strides with their support of Jquery and the ASP.NET MVC project.
From that perspective I think Microsoft is in a really good place right now. Webforms continues to serve that corporate environment that other companies don’t seem to care about and ASP.NET MVC allows them to challenge Rails et al. in the web space.
For shrinkwrap apps, internet apps, and anything where you really need polish, you care what your URLs look like, and you want a lot of control over what's going on so you can make it fast, shiny, professional, and bulletproof, the still-beta ASP.NET MVC has proven itself... stackoverflow.com is implemented with MVC and the team is loving it.
Stefan makes an excellent point that ASP.NET's original model was meant to be familiar and comfortable to old-school VB programmers, by providing a thick abstraction over HTML and HTTP that leaks really, really badly. For example half of your app stops working if JavaScript is turned off... even things that look like hyperlinks stop working because they're javascript under the covers... and for a timid VB programmer they suddenly have to deal with much, much more complexity to solve these last mile finishing touch kinds of things.
Conclusion... need a quick and dirty CRUD app for internal purposes that just has to be good enough? ASP.NET is fine... you'll barely have to write any code at all. Building a public-facing app that needs to be slick and polished? If you're using the Microsoft stack, start with ASP.NET MVC.