lecture: Marrying front with back end

Event_large

Most web frameworks are broken. They either just address the server side part of a web application (Rails, Symfony, Spring, Sinatra, ...) or the client side (ext.js, YUI, Backbone.JS, amber.js,…) resulting in duplicated code, inefficient implementations and lots of boilerplate code. Recent node.js based solutions like Yahoo's Mojito or Meteor are trying to change this, but what if you don't start development from scratch because of a large legacy codebase or not wanting to use 0.x versions?

This talk will feature and overview of an architecture that enables heavy reuse of even the smallest components by showing the details of the researchgate.net implementation. This approach enables developers to take page elements, like a single ""follow"" button, and place it everywhere on the site without having to duplicate any PHP, JS, HTML, CSS or AJAX endpoints in the process. Moreover it enables huge scalability, performance and UX improvements and should provide you with a couple of new ideas that are usually not explored in a classic (H)MVC approach.

Most web frameworks are broken. They either just address the server side part of a web application (Rails, Symfony, Spring, Sinatra, ...) or the client side (ext.js, YUI, Backbone.JS, amber.js,…) resulting in duplicated code, inefficient implementations and lots of boilerplate code. Recent node.js based solutions like Yahoo's Mojito or Meteor are trying to change this, but what if you don't start development from scratch because of a large legacy codebase or not wanting to use 0.x versions?

This talk will feature and overview of an architecture that enables heavy reuse of even the smallest components by showing the details of the researchgate.net implementation. This approach enables developers to take page elements, like a single ""follow"" button, and place it everywhere on the site without having to duplicate any PHP, JS, HTML, CSS or AJAX endpoints in the process. Moreover it enables huge scalability, performance and UX improvements and should provide you with a couple of new ideas that are usually not explored in a classic (H)MVC approach.