FRONTEND CHOICES
summary
Argues that modern front ends work best when split into two apps—a Rails API and a separate JS build—demonstrates using Angular and Ember, and shows practical tooling: Sprockets + Bower integration, the Ember Rails API layout, and a Grunt-based workflow with Grunt + Karma + Jasmine for fast tests. Describes building an Angular UI for OpenProject and a large Ember CRM that exposes immature JS tooling, recommends prerendering (PhantomJS or crawl services) or progressive enhancement for SEO rather than client‑only rendering.
AI-written summary · about
chapters (6)
- 0:00Start
- 1:21front end vs. frontend
- 4:33Single page v traditional HTML
- 12:09Room for Rails?
- 18:16trzy three practical usage
- 19:45gem install bower-rails
related talks
01h 07mModern Frontend Engineering
38mEmbrace the frontend revolution
38mThe Front-End Future
35mCrossing the Bridge: Connecting Rails and Your Front-End Framework
19mFrontend Meet Backend Get Along
34mYour Front End Framework is Overkill - Server Side Javascript w/ Rails
21mFrontend-centered Development: the Future of Web Development
46mMicro Frontend: the microservice puzzle extended to frontend
