Backbone.js vs Espresso.js: What are the differences?
Backbone.js and Espresso.js are both open source tools. It seems that Backbone.js with 27.5K GitHub stars and 5.7K forks on GitHub has more adoption than Espresso.js with 523 GitHub stars and 20 GitHub forks.
What is Backbone.js?
What is Espresso.js?
Want advice about which of these to choose?Ask the StackShare community!
Why do developers choose Espresso.js?
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Espresso.js?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Espresso.js?
Sign up to get full access to all the tool integrationsMake informed product decisions
When the data request returns, Backbone.js gets busy. The idea with Backbone is that we render each Model that comes down from the server with a View, and then Backbone provides an easy way to:
1) Watch for DOM events within the HTML generated by the View and tie those to methods on the corresponding Model, which re-syncs with the server
2) Watch the model for changes, and re-render the model’s HTML block to reflect them
Neat! Using that general approach, we get a fairly regular, comprehensible, and maintainable client. We custom-built a client-side Model cache to handle updates and simplify client-side Model reuse.
The main web store is a Backbone.js single page web application, and so it hits API endpoints to do all the calls, and we use those same API endpoints for the consumer iPhone app, the consumer Android app, and the consumer mobile web app. It worked out really nicely, us just building one API and just all these clients, including the web client, using that.
Major part of our UI application uses Backbone models and views extensively. Though there's a plan to migrate to React and Redux.