The Chirpolith: Successfully Migrating a Messy App to Ember
summary
Claims a yearlong migration that replaces a fragmented Backbone/Marionette/React landscape with a single Ember app, reusing legacy models and views first and then incrementally rewriting them; implements an instance initializer to translate hash URLs, uses iframes to avoid costly app merges, and measures progress with a bytes-count chart. Shows concrete results: 95 routes, 75 models, over 200 components; migration finishes largely transparent to users and successfully deletes most Backbone code.
AI-written summary · about
chapters (6)
- 0:00Introduction
- 1:19The Chirpolith
- 6:02Getting Started
- 12:56Rewriting
- 15:47Other Problems
- 20:24Staying Motivated
related talks
24mMigrating an Existing App to Ember, Component After Component
22mUsing Ember to Make the Seemingly Impossible Easy
25mThe Great Migration, Redesigning and Rewriting our App in Ember.js
22mUsing Ember to Make the Seemingly Impossible Easy
21mHow I Learned to Love Ember
33mEvergreen Legacy Applications
25mTwo Ember Apps Become One
32mAnimations and Transitions in an Ember App