[deleted]
Re:Backbone UI
by MatthewPhillips on Tuesday June 19, 2012 @09:35AM
(#4131681)
They're not really delivering an 11k library then, are they?
They are; they're just assuming you're already using jQuery (which for 95% of people using Backbone, is a correct assumption)
Agreed - laconic is a tough sell for me but I can get over that. However having JQuery required as well!? Too heavy now for any mobile web apps I'd planned.
Re:Backbone UI
by mkmcdonald on Tuesday June 19, 2012 @12:25PM
(#4132666)
[from the link]
> Backbone UI depends on Backbone, Underscore, jQuery, and laconic.
That's a disaster waiting to happen.
Re:Backbone UI
by joestelmach on Tuesday June 19, 2012 @12:34PM
(#4132704)
care to elaborate?
Re:Backbone UI
by mkmcdonald on Tuesday June 19, 2012 @12:42PM
(#4132745)
Requiring four separate APIs is a client-side dependency nightmare; requiring around 15k lines of uncompressed code is a disaster waiting to happen.
Well, it is a disaster that has been waiting for a while now. Several large production apps on that stack, and not really any problems.
I think the point is there may come the times when there two frameworks that depends on different version of dependencies. It could be the Backbone-UI and something else.
It would be okay if the consumer code is dependent on all the libraries. But if one of your framework is dependent on certain version of library and another one depends on another version of the said library, that is disaster waiting to happen. It would be hard to upgrade one framework , hence making it hard to move forward since your code is all tangled to all the frameworks.
Instead write your libraries to HTML standards, and provide links to polyfills that they'll need. Don't assume everyone is targeting IE6.