3 ms·
I recently finished building a large-scale app out in Backbone. It was a joy at first - I knew I needed a flexible framework that would work with the non-conve
by johnernaut 13y ago
I recently finished building a large-scale app out in Backbone. It was a joy at first - I knew I needed a flexible framework that would work with the non-conventional UI that I was to produce and Backbone worked out perfectly.
After reaching 45+ models and hundreds of view files (along with custom 'controller', 'presenter' and a long chain of inheritance objects that I had to produce if I didn't want to go insane), I'm finding the app to be a bit un-manageable at this point.
Another thing that's a huge pain with Backbone is it's router. The custom matching implementation for segments that was recently added is nice - but it doesn't work well at all with extremely dynamic URL's requiring tons of filtering options as query parameters (actually, there isn't any JS framework that I've seen handle that use-case well).
I'm currently in the process of re-building the same app out in Ember - it's going well so far, but I have a feeling I'm going to start pulling my hair out when I get to the more complex pages.