Rant: Backbone, Angular, Meteor, Derby
gist.github.com
Rant: Backbone, Angular, Meteor, Derby
1–10 of 163 posts
Re: Rant: Backbone, Angular, Meteor, Derby
#2Re: Rant: Backbone, Angular, Meteor, Derby
#3Re: Rant: Backbone, Angular, Meteor, Derby
#4actually, Meteor is not like Derby. For one, you don't need to deal with callbacks when data is changed. Meteor can automatically figure out what data sources are bound to certain containers in the template being rendered and when you make a change in the database, the data is pushed to all the clients. Here are some good details on the differences: http://news.ycombinator.com/item?id=3842525 . Also, Meteor now has a…
Re: Rant: Backbone, Angular, Meteor, Derby
#5Cached at https://gist.github.com/4454814 if down (my Drupal server has been miserable lately and I'm currently migrating to DocPad)
Re: Rant: Backbone, Angular, Meteor, Derby
#6Cached at https://gist.github.com/4454814 if down (my Drupal server has been miserable lately and I'm currently migrating to DocPad)
Re: Rant: Backbone, Angular, Meteor, Derby
#7However, as our Backbone application grew in complexity, we noticed that Backbone is so bare in terms of functionalities that we had to build our own half-baked framework on top of it to make up for the gaps.
I think the Backbone project needs to make Backbone's intentional feature sparseness clear. I've come to realize that backbone is more of a library which provides a basis to make a client-side framework rather than a something that can be used standalone by app developers.
If I could go back and change our original choice, I definitely would have gone with one of the Backbone-derived frameworks (chaplin, marionette) or just gone with something more fully-featured like angular. While backbone is beautiful and elegant for small projects, it just doesn't provide much convenience as a stand-alone library for larger applications.
Re: Rant: Backbone, Angular, Meteor, Derby
#8Re: Rant: Backbone, Angular, Meteor, Derby
#9actually, Meteor is not like Derby. For one, you don't need to deal with callbacks when data is changed. Meteor can automatically figure out what data sources are bound to certain containers in the template being rendered and when you make a change in the database, the data is pushed to all the clients. Here are some good details on the differences: http://news.ycombinator.com/item?id=3842525 . Also, Meteor now has a…
!! Those REST packes enable server-side routes? I remember the last time I checked, when Meteor had it's new "server pages" it was Phantom generated snapshots of client renders, which blew my mind. I'll explore those packages, that was my biggest gripe and may motivate me to take down my post.
There's a fuller explanation of our routing / REST plan here: https://trello.com/card/page-model-server-side-rendering-res...
Re: Rant: Backbone, Angular, Meteor, Derby
#10Recently decided to use Backbone as a JSMVC Framework on my team. Although I looked at Ember and Angular, which obviously both have many more features than backbone out of the box, We chose to use Backbone because it seems to have such a large and vibrant community behind it - seems like angular and ember are both lacking in this respect. However, as our Backbone application grew in complexity, we noticed that Backbo…