Re:Migrating a large JavaScript project from DOM spaghetti t...
by rimantas on Friday November 16, 2012 @02:38AM
(#4792874)
For anyone tempted: keep in mind, how trivial this example is.
When time comes to nontrivial things knockout will bite and bite you hard.
[ Parent
| on HN ]
Re:Migrating a large JavaScript project from DOM spaghetti t...
by riffraff on Friday November 16, 2012 @02:53AM
(#4792914)
while this is an interesting reply, it could be way more interesting if it contained a "because ...." subsentence, could you expand on this?
Re:Migrating a large JavaScript project from DOM spaghetti t...
by Offler on Friday November 16, 2012 @10:13PM
(#4797030)
We build online trading applications with KO (we use it only for the view, we have our own Presentation Model were we have observers which pretend to be KO observables) and we have found it quite helpful.
The components built are FX tiles, trade and order tickets.
Re:Migrating a large JavaScript project from DOM spaghetti t...
by thisone on Friday November 16, 2012 @03:53AM
(#4793049)
what do you mean by non-trivial?
I've abused knockout to some rather interesting ends, but I've never attempted to use it for as an in browser MVC setup.
I think of Knockout and Backbone as fulfilling two different purposes.
Re:Migrating a large JavaScript project from DOM spaghetti t...
by hasenj on Friday November 16, 2012 @03:52AM
(#4793045)
As opposed to Backbone, which doesn't bite you hard?
Dude Backbone only works for trivial examples, and even then, and I mean, even with trivial examples, Backbone is almost useless.
I haven't yet been bitten by Knockout in any bad way.
Re:Migrating a large JavaScript project from DOM spaghetti t...
by Cthulhu_ on Friday November 16, 2012 @04:18AM
(#4793100)
"Dude Backbone only works for trivial examples, and even then, and I mean, even with trivial examples, Backbone is almost useless."
I disagree. Backbone is a structuring framework; if you can't make it work with bigger projects, you're doing it wrong.