48 min listen
From build-time to run-time
FromFrontend First
ratings:
Length:
65 minutes
Released:
Feb 13, 2019
Format:
Podcast episode
Description
Topics include:
01:15 - Implementing Mirage's AddonDocs blog with GitHub issues
15:30 - Discussion forum vs. GitHub issues vs. blog comments
18:18 - Moving the blog post source to a GitHub issue
23:30 - Dynamic vs. static data, and implications for changing build-time data to run-time data.
27:40 - Downsides of run-time data
37:00 - SPA architecture and distributed systems. How does React/Vue "happy path" architecture differ from Ember's?
41:45 - Testing is the only true way to know if your dependencies work.
43:31 - Where does Ember pass the Celery Test, and where does it fail?
Links:
Artsy Engineering's blog post on using GitHub issues for blog post comments
Utterances
Tailwind's discussion forum
Basecamp's vocabulary doc, from their handbook
01:15 - Implementing Mirage's AddonDocs blog with GitHub issues
15:30 - Discussion forum vs. GitHub issues vs. blog comments
18:18 - Moving the blog post source to a GitHub issue
23:30 - Dynamic vs. static data, and implications for changing build-time data to run-time data.
27:40 - Downsides of run-time data
37:00 - SPA architecture and distributed systems. How does React/Vue "happy path" architecture differ from Ember's?
41:45 - Testing is the only true way to know if your dependencies work.
43:31 - Where does Ember pass the Celery Test, and where does it fail?
Links:
Artsy Engineering's blog post on using GitHub issues for blog post comments
Utterances
Tailwind's discussion forum
Basecamp's vocabulary doc, from their handbook
Released:
Feb 13, 2019
Format:
Podcast episode
Titles in the series (100)
Making the impossible, impossible: Sam and Ryan talk about their Functional CSS training at EmberConf, some ideas for hiding styling implementation details from templates, a new setup for multiple staging environments, an idea from data modeling called "Making the impossible, impossible", and how to use data down actions up effectively in forms. They also answer some listener questions. by Frontend First