A Round Table on The State of Front-End: (Ember, Angular, React)
summary
Panel debates concrete tradeoffs: Angular emphasizes decorators and ahead‑of‑time precompilation and is tied to Ionic for componentized mobile UIs; React claims simpler components, JSX, React Native for mobile and a marketplace of state tools (Redux, MobX) with create‑react‑app bootstrapping; Ember sells Ember CLI automates upgrades plus Glimmer, Ember Data and JSON:API conventions for long‑term maintainability; listeners judge on migration pain, tooling used, and whether apps built with these choices actually ship and stay maintainable.
AI-written summary · about
chapters (11)
- 0:00Start
- 2:39Interesting Things about Angular
- 7:15Component Model
- 8:36Functional Stateless Components
- 12:33Weakness with Ember
- 21:26Types of Apps Do You Think Angular Works Best for
- 26:26What Typescript Is
- 33:50How Is React Structured and Where Did It Come from
- 34:20React Native
- 42:40Ember Typescript Support
- 43:54Quality Assurance and Long-Term Maintenance within Your Framework
related talks
01h 10mThe Future of Frontend Panel
25mCreating the Ultimate Front End UI for a Single Page Application
40mFRONTEND CHOICES
08mInterview with Matt Creager
01h 02mChoosing a JavaScript Framework
38mWhat's The Framework of the Future?
40mAngular, React, Vue and Co. – peacefully united thanks to Web Components and Micro Apps
32mMiss the forest for the trees: How frontend developers fail to be engineers