I have been around the web business since the beginning of the commercial web era i.e. 1995 and I have been making web pages and application with the most of the web tools since then. From the day ASP.net web forms were released I could not help it but I did not like it, it had an approach that gave less control to the programmer and a attitude that I should not care about the client, the framework will handle the pluming that is necessary for delivering the content to the client.
From the beginning I try to code around the framework and each time it took allot of energy and allot of time from me, the framework was supposed to help me not be in the way for me. The server event driven idea is and was the most annoying part of the framework. To pass the clients event to the server and reinvent the event there so I could use an event driven model for the client events on the server??. I don’t have anything against the event driven model in particular, just the dumb idea to send the clients event over a stateless protocol to the server. And to overcome the stateless protocol, lets serialize the state and pass it around, wow that is a good idea, not…
The main problem is that the ASP.net web form framework don’t recognize the web client as an worthy component to handle the state and UX capabilities it self. If you accept that the web client can handle the state, and use XHR to let the client call services and get a response back that can change it’s state, then the server is only a simple service that that provides simple functions. That server don’t need a complex framework of junk to be a good service to the client. God dam Microsoft invented XHR why could they not embrace it them self!
No comments:
Post a Comment