SUSE Studio has evolved a number of methods for performing dynamic client updates; in some places, we use Rails 2.0-style RJS - sending rendered partials along with JS code to be executed by the client. In other places, we're sending JSON data, and handling it via custom-written interactions. Most recently, we've experimented with client-side rendering of Mustache templates. None of these approaches is particularly robust or maintainable, and as a result we've ended up with a huge amount of fragile client-side code.
Luckily, we're not the only developers in this situation - every major web application faces the same challenges. As a result, a number of client-side frameworks have developed, applying common design patterns to build up a logical, maintainable framework for managing client-state and server interactions for web development. The problem is that everyone seems to have a solution, and that means navigating a number of projects to find a good fit.
Scoop.it!
No comment yet.
Sign up to comment