Re: ASP.NET: Fundementally Flawed Architecture

Henry wrote:
We are all familiar with the larval stage of a RAD programmer; all the application's code is in event handlers, and each form is an independent application. Enlightenment usually dawns when the programmer needs to coordinate two forms, as a consequence of them being parts of the same application, and some meta-form code must be written.

Now write an ASP.NET application. What do you get? Unless you make strenuous efforts, battling the framework and IDE all the way, each page is a separate application, with very limited opportunity for passing state between pages. (The component model and page life-cycle also become your bitter enemies at this point.) There is no high-level view, unless you write your own MVC, in which case you're a lot better off with Ruby on Rails.

Yea, the whole web browser application philosophy is crap.

People just seem to fall for any new horse*** that comes along.

Thinking on a higher level and not getting caught up in the newest fad will get you where you need to be.
.