Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

How to start with Backbone.js: A simple skeleton app

codeartists.com

Post reply on HN
Print view View original

41–49 of 49 posts

Re: How to start with Backbone.js: A simple skeleton app

#41

Post by xpose2000 »

king_magic wrote: post #2

"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 could not agree more. Though I would replace "minor" frustration with "major".

Re: How to start with Backbone.js: A simple skeleton app

#43

Post by hakaaak »

Why start with Backbone.js? Why not use AngularJS instead and decrease implementation time? The primary reason to use backbone would be that you are trying to retrofit some existing page or services, and if you are doing that, you are going to spend a hell of a lot of time that you could just spend rewriting it all in angular and have less code when you are done.

Re: How to start with Backbone.js: A simple skeleton app

#44

Post by hakaaak »

camus wrote: post #33
Kiro wrote: post #23

Earlier quoted context omitted.

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 model…

Backbone is not like Sinatra. Backbone is a hell of a lot more work than Sinatra. Backbone is a framework that more easily can fit atop existing design and services, however it takes so much time and in the end you just have even more complex spaghetti for someone else to maintain when you leave.

Re: How to start with Backbone.js: A simple skeleton app

#45

Post by camus »

hakaaak wrote: post #44
camus wrote: post #33

Earlier quoted context omitted.

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 model…

Backbone is not like Sinatra. Backbone is a hell of a lot more work than Sinatra. Backbone is a framework that more easily can fit atop existing design and services, however it takes so much time and in the end you just have even more complex spaghetti for someone else to maintain when you leave.

not it's not , the idea was "relativity" not "comparaison". Backbone doesnt do serverside request handling , nor does AngularJS.

Re: How to start with Backbone.js: A simple skeleton app

#46

Post by tcgv »

camus wrote: post #32
jtchang wrote: post #22

Earlier quoted context omitted.

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"…

AngularJS solves app architecturing problems in a elegant declarative way

Actually BackboneJS praises itself for not doing that:

It doesn't depend on stuffing application logic into your HTML. There's no embedded JavaScript, template logic, or binding hookup code in data- or ng- attributes, and no need to invent your own HTML tags. [1]

[1] http://backbonejs.org/#FAQ-why-backbone

Re: How to start with Backbone.js: A simple skeleton app

#47

Post by bhataktiatma »

king_magic wrote: post #2

"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…

> HAML, SASS and CoffeeScript

Only a total idiot will use these in a tutorial. OP: Stop submitting your idiotic shit to HN.

Re: How to start with Backbone.js: A simple skeleton app

#48

Post by camus »

tcgv wrote: post #46
camus wrote: post #32

Earlier quoted context omitted.

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"…

AngularJS solves app architecturing problems in a elegant declarative way Actually BackboneJS praises itself for not doing that: It doesn't depend on stuffing application logic into your HTML. There's no embedded JavaScript, template logic, or binding hookup code in data- or ng- attributes, and no need to invent your own HTML tags. [1] [1] http://backbonejs.org/#FAQ-why-backbone

yet one still needs to solve these problems somehow...

Re: How to start with Backbone.js: A simple skeleton app

#49

Post by scott_w »

kyllo wrote: post #11
king_magic wrote: post #2

"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…

AFAIK you don't necessarily need to use HAML, SASS, and CoffeeScript in order to use Backbone. They are tools that you can "plug in" to your web application to make you more productive, but I think they deserve separate treatment. And you need a server but it doesn't have to be Sinatra or anything written in Ruby. But Sinatra is as good a choice as any. If you're going to study Backbone, it might be better to just st…

"you're a web developer and should already be familiar with HAML, SASS, and Coffee"

That's like saying a web developer should be familiar with Ruby.

Unless you've made a conscious decision to use it, there's no reason to assume that you're familiar with the tools in question.

For what it's worth, I can see myself needing Backbone (or something similar) for what I'm working on, but there's no way I'll be using CoffeeScript.

Post reply on HN