3 ms·
Seems neat, but it would have been nice to differentiate itself from backbone a little more upfront. The sites even look similar. The key architectural differ
by netghost 16y ago
Seems neat, but it would have been nice to differentiate itself from backbone a little more upfront. The sites even look similar.
The key architectural difference seems to be that the ui is updated before the server responds, which is great in a single user situation, but can get pretty inconsistant once you're in a multi user app.
I do have to say that I like the patterns section at the end, it's always good to see a prescription for how you would use a library or framework.
- jashkenas 16y agoThat's actually not an architectural difference. In Backbone, when you call .save(), the attributes update instantly, and the changes are synced to the server asynchronously.
- netghost 16y agoThat was the main difference pointed out in the documentation. I guess I'd have to try it out to see how it differs in practice.
- flippyhead 16y agoYeah, my very initial reaction was that this must be a joke of some kind -- I see that it's not -- but boy it seems so similar on the surface
- armandososa 16y agoSeems neat, but it would have been nice to differentiate itself from backbone a little more upfront. The sites even look similar. I agree. For a moment I thought it was a parody.
- probst 15y agoSo did I! I thought it was a spoof of backbone although I couldn't really understand what the reason for the parody was, so I kept on reading to see what it was all about. Even the name suggests it is a backbone "clone". Edit: Upon reading more about it, it sounds like a really nice framework. A shame it is branded so similarly to backbone which is bound to result in people fighting about which is better, spine or backbone, instead of seeing it for its own merits.
- armandososa 15y agoYeah, The name makes it fell kinda like those "php on tracks" rails spin-offs. But it's definitely on my list of nice things to try.
- secoif 16y agoYou can create new Models independent of the Collection and they will sync to the server asynchronously when you Collection#add() them, but note that all of the Backbone events ('add','success', etc) are triggered in response to the server. It'd be nice if this was more clear, and perhaps Backbone could trigger additional events based solely on clientside actions...