Espresso.js vs Marionette: What are the differences?
Espresso.js and Marionette are both open source tools. It seems that Marionette with 7.15K GitHub stars and 1.35K forks on GitHub has more adoption than Espresso.js with 523 GitHub stars and 20 GitHub forks.
What is Espresso.js?
What is Marionette?
Need advice about which tool 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?
What are the cons of using Marionette?
Sign up to get full access to all the companiesMake informed product decisions
The front end for Heap begun to grow unwieldy. The original jQuery pieces became difficult to maintain and scale, and a decision was made to introduce Backbone.js, Marionette, and TypeScript. Ultimately this ended up being a “detour” in the search for a scalable and maintainable front-end solution. The system did allow for developers to reuse components efficiently, but adding features was a difficult process, and it eventually became a bottleneck in advancing the product.
Today, the Heap product consists primarily of a customer-facing dashboard powered by React, MobX, and TypeScript on the front end. We wrote our migration to React and MobX in detail last year here.
We are in the middle of a change of the stack on the front end. So we used Backbone.js with Marionette. Then we also created our own implementation of a Flux kind of flow. We call it eb-flux. We have worked with Marionette for a long time. Then at some point we start evolving and end up having a kind of Redux.js-style architecture, but with Marionette.
But then maybe one and a half years ago, we started moving into React and that's why we created the Eventbrite design system. It's a really nice project that probably could be open sourced. It's a library of components for our React components.
With the help of that library, we are building our new stack with React and sometimes Redux when it's necessary.