Ember.js vs React Storybook
Overview
Share your Stack
Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.
CLI (Node.js)
Manual
Detailed Comparison
A JavaScript framework that does all of the heavy lifting that you'd normally have to do by hand. There are tasks that are common to every web app; It does those things for you, so you can focus on building killer features and UI. | You just load your UI components into the React Storybook and start developing them. This functionality allows you to develop UI components rapidly without worrying about the app. It will improve your team’s collaboration and feedback loop. |
Creating web apps;Building UI | Isolated environment for your components (with the use of various iframe tactics);Hot module reloading (even for functional stateless components);Works with any app (whether it's Redux, Relay or Meteor);Support for CSS (whether it's plain old CSS, CSS modules or something fancy);Clean and fast user interface;Runs inside your project (so, it uses your app's NPM modules and babel configurations out of the box);Serves static files (if you host static files inside your app);Deploy the whole storybook as a static app;Extendable as necessary (support for custom webpack loaders and plugins) |
Statistics | |
GitHub Stars 22.6K | GitHub Stars - |
GitHub Forks 4.2K | GitHub Forks - |
Stacks 1.6K | Stacks 635 |
Followers 865 | Followers 355 |
Votes 775 | Votes 0 |
Pros & Cons | |
Pros
Cons
| Cons
|
Integrations | |
What are some alternatives to Ember.js, React Storybook?
AngularJS
AngularJS lets you write client-side web applications as if you had a smarter browser. It lets you use good old HTML (or HAML, Jade and friends!) as your template language and lets you extend HTML’s syntax to express your application’s components clearly and succinctly. It automatically synchronizes data from your UI (view) with your JavaScript objects (model) through 2-way data binding.
Vue.js
It is a library for building interactive web interfaces. It provides data-reactive components with a simple and flexible API.
Backbone.js
Backbone supplies structure to JavaScript-heavy applications by providing models key-value binding and custom events, collections with a rich API of enumerable functions, views with declarative event handling, and connects it all to your existing application over a RESTful JSON interface.
Angular
It is a TypeScript-based open-source web application framework. It is a development platform for building mobile and desktop web applications.
Aurelia
Aurelia is a next generation JavaScript client framework that leverages simple conventions to empower your creativity.
Mithril
Mithril is around 12kb gzipped thanks to its small, focused, API. It provides a templating engine with a virtual DOM diff implementation for performant rendering, utilities for high-level modelling via functional composition, as well as support for routing and componentization.
Marionette
It is a JavaScript library with a RESTful JSON interface and is based on the Model–view–presenter application design paradigm. Backbone is known for being lightweight, as its only hard dependency is on one JavaScript library, Underscore.js, plus jQuery for use of the full library.
Ampersand.js
We <3 Backbone.js at &yet. It’s brilliantly simple and solves many common problems in developing clientside applications. But we missed the focused simplicity of tiny modules in node-land. We wanted something similar in style and philosophy, but that fully embraced tiny modules, npm, and browserify. Ampersand.js is a well-defined approach to combining (get it?) a series of intentionally tiny modules.
Durandal
Durandal is a cross-device, cross-platform client framework written in JS and designed to make Single Page Applications (SPAs) easy to create and maintain.
PrimeNg
It has a rich collection of components that would satisfy most of the UI requirements of your application like datatable, dropdown, multiselect, notification messages, accordion, breadcrumbs and other input components. So there would be no need of adding different libraries for different UI requirements.
