Google should really add Backbone.js to Libraries API.
Backbone.js Fundamentals
41–50 of 83 posts
Re: Backbone.js Fundamentals
#42[deleted]
Re: Backbone.js Fundamentals
#43A side question, which seems worth asking as long as this is floating at the top of HN ... We try to rotate in fresh projects into the list of Backbone apps on the homepage: http://backbonejs.org/#examples ... but there are often many more interesting things out there in the wild than we're necessarily aware of -- for example: Rdio, the new GoogleArtProject.com, and Pitchfork.com. Are you currently working on a fun B…
[deleted]
Re: Backbone.js Fundamentals
#44My team just finished building two new features of our application using Backbone and now we're actually looking into switching to Ember.js to take advantage of the automatic databinding and lack of a need to do manual DOM manipulation.
Can anyone comment on their experience with the two frameworks?
Re: Backbone.js Fundamentals
#45The online version[1] was submitted 10 days ago[2] (by someone else) but it didn't get any attention. So I submitted a link to the epub version. It seems like a very good tutorial and I hope someone finds it useful. [1]: http://addyosmani.github.com/backbone-fundamentals [2]: http://news.ycombinator.com/item?id=3784854
Also, I'm watching a terrific presentation from the book's author right now: Large-scale JavaScript Application Architecture Developers creating JavaScript applications these days usually use a combination of MVC, modules, widgets and plugins for their architecture. They also use a DOM manipulation library like jQuery. Whilst this works great for apps that are built at a smaller-scale, what happens when your project…
Is there video of this? I find slides often miss out on things their author says on stage.
Re: Backbone.js Fundamentals
#46My team just finished building two new features of our application using Backbone and now we're actually looking into switching to Ember.js to take advantage of the automatic databinding and lack of a need to do manual DOM manipulation. Can anyone comment on their experience with the two frameworks?
For those who (like me) haven't heard of Ember.js before, it's SproutCore 2.0 (a complete re-architecture by the looks of it).
Re: Backbone.js Fundamentals
#47Earlier quoted context omitted.
Also, I'm watching a terrific presentation from the book's author right now: Large-scale JavaScript Application Architecture Developers creating JavaScript applications these days usually use a combination of MVC, modules, widgets and plugins for their architecture. They also use a DOM manipulation library like jQuery. Whilst this works great for apps that are built at a smaller-scale, what happens when your project…
Is there video of this? I find slides often miss out on things their author says on stage.
I don't think so. But this particular presentation (130 slides!) has tons of text on each slide that kinda works like a presenter...
Re: Backbone.js Fundamentals
#48A side question, which seems worth asking as long as this is floating at the top of HN ... We try to rotate in fresh projects into the list of Backbone apps on the homepage: http://backbonejs.org/#examples ... but there are often many more interesting things out there in the wild than we're necessarily aware of -- for example: Rdio, the new GoogleArtProject.com, and Pitchfork.com. Are you currently working on a fun B…
How can you tell that Pitchfork.com is using backbone?
Re: Backbone.js Fundamentals
#49I was thinking of learning Backbone soon until I read about Meteor yesterday. Is there any point in learning Backbone, or should I just go the Meteor route?
Your question strikes me as an odd one. Meteor just came out. I'm not sure that there are any folks who have built any substantial systems using Meteor yet (aside from it's authors) who would be able to give you a firm recommendation. That said, Meteor and Backbone do different things. Meteor is an attempt to solve (obviate, really) the mismatch between client/server development. To what extent it does this in a reas…
I'm a newbie, although I feel somewhat informed on these subjects (although not skilled in coding).
Anyway, I like the idea of using javascript everywhere. I plan on building smaller apps that are only client side. But I wonder if there is a cohesive method yet of using javascript everywhere.
Obviously meteor was big news yesterday, but it's quite immature. The YUI Mojito project also recently made news and is more stable/robust. While the tightly integrated approach used in YUI sounds convenient, I get the impression that there isn't much excitement behind YUI -- certainly not like backbone.js, node.js, et al.
So is there a collection of libraries that can play together well to make for an all javascript environment (i.e., backbone (plus underscore, jQuery) on the client, node + socket.io on the server)?
Re: Backbone.js Fundamentals
#50A side question, which seems worth asking as long as this is floating at the top of HN ... We try to rotate in fresh projects into the list of Backbone apps on the homepage: http://backbonejs.org/#examples ... but there are often many more interesting things out there in the wild than we're necessarily aware of -- for example: Rdio, the new GoogleArtProject.com, and Pitchfork.com. Are you currently working on a fun B…
http://openhercules.com is a backbone app
Off topic but I love your explanation of the openhercules name.
Edit: just played with the sample list and the keyboard interaction is pretty impressive too. Nice work.