rhysbb
Building a better debounce
Promise/A+ patterns
Backbone at Dataminr
The main issue as I see it is that people choose a framework for a project in a short period of time and larger frameworks tend to take time before you see where they shine. I hear people's reason for going with Backbone because it was really the first major MVC out there and because of it's popularity. When I hear why people go with another framework it's because of features - not popularity.
Add on to this whenever I've talked to people or read blogs on systems made with other frameworks the majority of talks on backbone are how to solve problems they encountered while talks about larger frameworks are how to use new features and get more from your code. Maybe it's just because Backbone has been around longer that we've all had more time to find the hardships, I don't know but time will tell.
Is it FUD to say all this? Probably a little, but if we don't have any fear, uncertainty or doubt when taking on a new project then you probably haven't got any idea what you're getting yourself in to.
Breaking it down with algoritms I: the round table
Using JQuery Functionally
4. Just create a object store that acts as a factory that will return the same object. In plastronJS there is already an mvc.Store that does this for you.
6. I built on top of goog.ui.Component that has a dispose() method that gets called automagically. I added in methods on the control that will dispose the event handlers when the control is disposed (plus it only has on handler for each type and will react based on an element test).
7. I like the router separate as it decouples the routing string. Instead I use a route and then have a mediator broadcast the new route which controls can listen to.
9. Why would you do this? if you are then you're doing it wrong.
PlastronJS an MVC for Closure Tools
An MVC for people who want to start using https://developers.google.com/closure/ A quick intro and todo app tutorial can be found here: http://rhysbrettbowen.com/2012/04/plastronjs.html and github with lots of docs, tests and a read me here: https://github.com/rhysbrettbowen/PlastronJS I'm planning to release some videos on the blog to go over it's design as well as more information about other...
"Or, don’t trust what “wise” elders tell you."
"My recommendation: learn the language, and use it to your liking; and don’t rely or blindly accept what any “wise elders” tell you. Try to do something new and crazy every day. You might not end up using the crazy, but it’s the best way to master JavaScript. Develop your own style that you are comfortable with. Experiment."
these points are still up for argument, but really they are pretty trivial. __You__ should __experiment__ with them and see if they are okay to use for yourself. The main trick will be if they make your code easier to understand and/or perform better _everywhere_. As long as it helps one of those cases without the detriment of the other then go ahead, just be aware of why people argue over them.