Framework · 2011–2020 · Cloud Scale

Ember.js

Convention-over-configuration SPA framework. LinkedIn and Discourse kept the faith; everyone else went React.

Why Ember.js faded

Ember faded because it optimized for long-lived enterprise SPAs while the market wanted hireable React freelancers. It was opinionated in the right ways but shipped heavy defaults in the era of bundle-size audits. Survivors swear by it; newcomers never arrive.

frontend spa conventions

Case studies

The three-year frontend migration that shipped parity — Multi-year rewrite; feature freeze periods; hiring for frameworks users never asked about

Patterns

Framework churn

2010–2016

Cloud Scale

Part of the Cloud Scale era (2010–2016).

Read the Cloud Scale era →

Compare with

vs AngularJS (1.x)vs Backbone.js vs React vs J2EE / EE frameworks

Related

Framework · 2010–2021

AngularJS (1.x)

Two-way binding magic that became a migration tax. Angular 2+ was a rewrite; the 1.x apps lingered for years.

Framework · 2010–2016

Backbone.js

Minimal structure for early client MVC. Taught the browser to think in models before React rewrote the rules.

Framework · 2013–now

React

Components and unidirectional data. Won the front-end by being good enough and having a gravitational ecosystem.

← Timeline Open graph Costliest fads