Side effects aren't declarative. What if they were?
from Frontend First Hosted by Frontend First
Topics include: 0:53 – Metaphysics and JavaScript by Rich Harris, and declarative side effects 15:26 – An Ember example that would be improved by hooks and declarative side effects 23:46 – Pitfalls and escape hatches when using hooks 35:40 – Rich's argument that rendering isn't even a declarative function of state, let alone side effects 41:42 – Deeper dive into useEffect docs 1:01:41 – Thought experiment on effects that sync with different data stores Sponsors: Next Release, mention EmberMap when you sign up for a trial and get 10% off Links: Metaphysics and JavaScript, by Rich Harris React's useEffect
Embed this episode
What this episode covers
Sam and Ryan talk more about their recent experience working with React Hooks. They dive into useEffect, talk about how the hooks paradigm encourages UI developers to think about their application's side effects declaratively, discuss whether the paradigm is too much of a departure from real-world stateful UI development, and compare it to working with side effects in Ember applications.
No transcript yet.