Please excuse me pimping my own site, but if you use PHP & MySQL - this will generate a basic working app that uses backbone.js extensively. As an example backbone app, I think it may need a few improvements to go along with the latest release as far as view binding goes. But, I feel like I plowed my way through a few common web app needs that aren't so obvious with backbone collections (sorting, pagination, filterin…
it is not trés bon , but très bon , if you intended to write something in french.
I use AngularJS for everything now, I find it much easier to use and more convient than backbone.
Why the hell is this comment on the bottom? I started with backbone and was like...wtf is this. Then I went to knockout and it is what I am using now. I used Angular in a pet project a few weeks ago and was totally blown away at how easy it was. Angular is more suited to projects where you use it from the get go. I really like knockout because it is good to integrate in existing projects.
AngularJS is great ( my first app every with Angular :
http://paraiso-flickr-search.herokuapp.com
AngularJS forces developpers into separation of concerns , DI , which are good things , but until one understands why they are good , one will not like AngularJS.
Backbone is in my opinion more a library ( like jQuery ) than a framework. it doesnt force people doing anything , it provides helpers and conveniant "classes" to work with.
But it doesnt solve most of the problems regarding app architecture. AngularJS solves app architecturing problems in a elegant declarative way ( like Flex before it ).
I use AngularJS for everything now, I find it much easier to use and more convient than backbone.
I see these comments in every Backbone thread and no-one seems to disagree. Is Backbone that bad?
The difference between Backbone and Angular is that AngularJS is more like Rails whereas Backbone would be more like Sinatra. What it means is , for complicated apps , you'll have to do complex stuffs anyway , so 'complicated' features are better built in the framework itself.
Unless you use a plugin , you'll have hard time updating your views automatically in Backbone if your model has nested objects. And your models cannot be arrays. In AngularJS it doesnt matter.
I played around with backbone.js for a couple of days and gave up. The documentation is there but it doesn't help someone who knows 0% about the concept.
Then I tried Knockout.js - It has a very nice quickstart. http://learn.knockoutjs.com/ - after a few days playing around with it, I started on my project.
God, there are a billion Todo and Skeleton apps and hardly any that give you the principles to build a serious Backbone.js app. It's great, minimal, flexible and incredibly easy to use in a backward and convoluted way if you don't have something good to guide you. Also, throwing HAML, SASS, Coffeescript, autogeneration and more into this makes this just... that much less useful.
"How to start with Backbone.js: A simple skeleton app" first sentence: "You need a solid knowledge of JavaScript, familiarity with Backbone, Ruby, HAML, SASS and CoffeeScript to find this writeup useful." Feels like an awful lot of prereqs for a starter. I don't expect to be spoon-fed JavaScript basics, but I feel like too many Backbone guides presume some understanding of Backbone before starting with something that…
i actually wish there were more blogs that assume this level of background. i know what backbone is, i know what it's competition is, and i want to play with nontrivial working examples without having to figure it out myself from the api docs.
I played around with backbone.js for a couple of days and gave up. The documentation is there but it doesn't help someone who knows 0% about the concept. Then I tried Knockout.js - It has a very nice quickstart. http://learn.knockoutjs.com/ - after a few days playing around with it, I started on my project. Good resources: Knockout.js Documentation http://www.knockmeout.net/ Stackoverflow
Knockout.js is great. It doesn't force a whole framework on you. It is straight forward to use. You can slide it in into an existing project easily. I use it from turning pages to be merely more interactive to full fledged single-page app.
Please excuse me pimping my own site, but if you use PHP & MySQL - this will generate a basic working app that uses backbone.js extensively. As an example backbone app, I think it may need a few improvements to go along with the latest release as far as view binding goes. But, I feel like I plowed my way through a few common web app needs that aren't so obvious with backbone collections (sorting, pagination, filterin…
it is not trés bon , but très bon , if you intended to write something in french.
jQuery, Underscore, Backbone, require.js, text.js (require.js plugin), r.js (require.js optimizer) is the setup I've been using on new projects for about a year now and I love it. I love Backbone's models and collections. It took a while to come to terms with the get and set methods and nested objects is just a bit of a hassle (but that keeps me thinking twice about what I'm doing). I like the views but I find I'm repeating myself quite a bit and I've been meaning to extend Backone.View with a few conventions of my own, which is exactly the kind of thing Backbone was intended for. Require.js lets me modularize everything. the text.js plugin lets me keep markup in html files which get converted to JS functions during optimization with r.js. During development I have everything nice and separated for debugging and optimization before deployment jams everything up into 1 file. I have a bash script that generates a new project with the basic require.js config including shim settings needed for Underscore and Backbone and usually the localStorage plugin because that's real nice if you don't have actual services wired up yet. This setup is what made me start to enjoy front-end development.