4 ms·

I don't believe any of those apply to this library. But indeed those were the issues with Backbone at the time. Check out an example app: https://github.com/a

• ricardobeat 4y ago
  The infinite loop for example, is easy to get with a circular chain: 'change' -> .listenTo subscriber -> triggers another change. Probably won't happen in a single file, but because updates can come from anywhere, as an app grows you are exponentially more likely to accidentally get one. The example demonstrates a couple of the downsides, like directly wiring listenTo -> render, but it has no child views or interaction between different models / collections. With a bit more complexity I'm sure it would hit all of those points. Did you ever end up building a production app with the library?
  • akrymski 4y ago
    Yes I've written several apps with it. It does have child views (to do item). You can't get a circular chain any more than with react. ListenTo is written manually only for special cases there, otherwise a controller is simply bound to a model and it's all handled for you.