Ember on Rails: #REALTALK
summary
A developer goes from zero to shipping a UX‑centric app that pulls shared links from Twitter and becomes an animated‑gif browser, using Rails as the API and Ember.js on the front end. Getting started costs months of friction (about eight months of experimentation) but a basic app renders in hours; persistence uses ember-model instead of Ember Data, templates use Handlebars, routing uses the history API, and computed properties drive live counts. Many rough betas are encountered but the demo works.
AI-written summary · about
chapters (6)
- 0:00Start
- 1:5780% USE CASE
- 9:39MODELS ARE MOSTLY WHAT YOU EXPECT
- 10:01APP_ROUTER.JS IS WHAT YOU KNOW AS "ROUTES"
- 18:40DATA. AUTHENTICATION.
- 22:07PLEASE, DON'T GIVE ANOTHER TALK ABOUT WHY COMPUTED PROPERTIES ARE GREAT
related talks
22mUsing Ember to Make the Seemingly Impossible Easy
35mEmber on Rails - Convention over Configuration on both sides of the tubes
22mUsing Ember to Make the Seemingly Impossible Easy
34mA Rail's Developers Intro to Ember
26mAmbitious UX for Ambitious Apps
21mHow I Learned to Love Ember
19mBuilding Real-Time Applications with Ember
24mAn Illustrated Guide to Ember