3 ms·
Yes, I didn't mean to dismiss backbone as a whole by any means. It's in fact on my "try asap" list (still undecided whether backbone or knockout is the way to g
by moe 16y ago
Yes, I didn't mean to dismiss backbone as a whole by any means. It's in fact on my "try asap" list (still undecided whether backbone or knockout is the way to go).
With modularity I don't strictly mean LOC. Rather I think that most of these lines in the address plugin are probably in there for a good reason. Thus if backbone ships its own solution to the problem, but that solution covers only part of what I need, then I'd have to integrate both - and perhaps deal with conflicts. That would be undesirable.
On the other hand I recognize that introducing dependencies to specific other plugins is also undesirable. I'm a bit torn about which is the lesser evil here.
- jashkenas 16y agoIf the solution only covers part of what you need, then that is indeed a problem that should be fixed ... by covering all of what you need. On the other hand, I'll leave it up to your judgement whether the lines in the address plugin are necessary. You can compare implementations here: https://github.com/asual/jquery-address/blob/master/src/jquery.address.js https://github.com/asual/jquery-address/blob/master/src/jque... http://documentcloud.github.com/backbone/docs/backbone.html#section-77 http://documentcloud.github.com/backbone/docs/backbone.html#... If 90% of Backbone apps end up using Controllers, it's better to include a concise implementation than a heavy dependency, I think.