November 13, 2019
Yehuda Katz on Paradigms vs. Abstractions in UI Development
The EmberMap Podcast
How to listen
Watch above, or find us on your favorite channel:
- 1:46 – Exploring the React paradigm
- 11:45 – How have your opinions on UI dev changed since starting Ember?
- 16:00 – How React's render functions and Ember's templates both solve the same problem: how to restrict the rendering code that users write
- 40:13 - Hooks and the importance of lifecycle entanglement
- 53:58 – The ES module spec, ES imports, and ES modules vs. CJS modules
- 1:04:55 – Are TypeScript users at risk of the same kinds of syntax collisions that CoffeeScript users once were?
- 1:10:10 – TypeScript now doesn't ship unstable features. (e.g. Optional chaining is stage 3)
- 1:15:35 – Yehuda's take on stage 0 through stage 4 ECMAScript proposals
- 1:23:39 – What's missing from UI development? And the difference between paradigms and abstractions.
- 1:31:00 – Ember's original sin was push-based reactivity. Pull-based is how programs work.
- 1:40:30 – Ember needs a new lifecycle entanglement primitive, that borrows concepts from both Hooks and Ember Concurrency tasks
- 1:57:07 – How do you feel about UI development in 2019?