Please login or sign up to post and edit reviews.
Which concepts should a framework teach?
Podcast |
Frontend First
Media Type |
audio
Categories Via RSS |
Technology
Publication Date |
Dec 20, 2019
Episode Duration |
01:09:47

Topics include:

- 0:40 – Which concepts should a framework be responsible for teaching?

- 7:20 – What does it actually take for someone to start using a framework? And Vue's multiparadigm approach.

- 16:32 – What if Ember Data wasn't part of Ember?

- 29:50 – Functional digression

- 37:00 – Back to Ember Data!

- 43:34 – When paradigms conflict with each other

- 49:46 – Back to Ember Data, again!

 

Links:

- [Vue composition API](composition-api-rfc.netlify.com">https://vue-composition-api-rfc.netlify.com)

- [MobX](https://mobx.js.org/README.html)

Sam and Ryan talk about the actual vs. perceived boundaries between Ember and Ember Data, and what it would look like if Ember Data were more separate from Ember than it has been historically. They also chat more generally about which concepts should be taught by official framework documentation, as well as a digression into APIs that appear impure but that are actually functionally pure.

Topics include:

- 0:40 – Which concepts should a framework be responsible for teaching?

- 7:20 – What does it actually take for someone to start using a framework? And Vue's multiparadigm approach.

- 16:32 – What if Ember Data wasn't part of Ember?

- 29:50 – Functional digression

- 37:00 – Back to Ember Data!

- 43:34 – When paradigms conflict with each other

- 49:46 – Back to Ember Data, again!

 

Links:

- [Vue composition API](composition-api-rfc.netlify.com">https://vue-composition-api-rfc.netlify.com)

- [MobX](https://mobx.js.org/README.html)

This episode currently has no reviews.

Submit Review
This episode could use a review!

This episode could use a review! Have anything to say about it? Share your thoughts using the button below.

Submit Review