
Blurring of MVC lines: Programming the Web Browser.

When HTML first came out, browsers could have been called "Application Thin Clients", if the buzzword had been in use at the time. The introduction of javascript made it possible to execute code on the client, and this turned browsers into something much more than just a "display" mechanism.
Before Javascript, Web application development was simple: everything was done server-side. The concept of MVC - Model View Controller - was easy: the HTML was generated, and that was the view. With Javascript being a full-blown programming language, the lines are being blurred between which code is responsible for the View, the Controller and even the Model. The resultant split of responsibility across client and server in wildly diverse programming languages is driving many developers to alternative technologies such as Flash, and causing headaches for those Web developers who remain.
The key components of the solution - to allow the developer to create MVC
applications in a single programming language, where at least the
"View" source is extracted and compiled to Javascript and HTML - actually
exist and are used in production environments, thanks to
Google Web Toolkit and
Pyjamas.
RubyJS is well on the
way, too.

Leave a comment