elabs/serenade.js — Issue #5: Event bindings and routing questions
Author: dariocravero
Created: 2012-02-01 02:02:47+00:00
State: open

Hey guys,

How're things?

First of all, I'd like to say thanks for releasing Serenade.js. It looks like a grea evolution on the concept itself -but you already know that hehe :)

One of the things I really liked was how thin controllers get when binding events directly on the view/template. It reminds me the first time I saw Sinatra and their inline-no-extra-files-routes :). It looks very concise, telling exactly what will be executed when interacting with that element. I have a qquestion regarding its readability though. How do a growing number of bindings affect how easy it's to read and follow right now? I don't know how complex are the apps you've built on the framework so far -btw, it'd be great if you could list any :)- but your experience will definitely shed some light.

There's one thing that most MV* frameworks tend to do out of the box these days and that's the ability to route stuff through the URL. I noticed that you leave that to other frameworks like Express.js, but that's server side... Is there any particular reason why you didn't bake it in?

Once again, thanks a million and keep the good work up!! :)