Sam and Ryan talk about the tradeoffs between shipping a single bundle of code vs. the route-based code splitting approach used by many tools like Gatsby and Next. They also talk about their recent experiences building with React, and whether web developers should compete with native experiences or embrace what the web has to offer. Topics include:- 2:38 – In React, there are no components- 13:45 – The feeling of momentum in React- 23:33 – SPA bundles vs. per-page code splitting- 45:33 - Conceptual code splitting, and web experiences vs. native experiences- 1:06:30 – React.Children utilities Links:- [Domain Modeling with Mirage JS training](https://www.youtube.com/watch?v=lfDBb0Ar-rc)- [Mirage JS Inspector Livestream 1](https://www.youtube.com/watch?v=WTDj7MXzejc)- [Mirage JS Inspector Livestream 2](https://www.youtube.com/watch?v=odcfQAwYGrc)- [Mirage JS Inspector Livestream 3](https://www.youtube.com/watch?v=knSI60CTZ-U)

Topics include:0:44 - Tailwind UI4:27 - Framework-agnostic tools11:44 - Logux33:31 - Next, code on the edge, static websites, and cachingLinks:Software Engineering DailyTailwind UILoguxNext.js 9.3

Yehuda Katz joins Sam to talk about the strategies Ember's developed to keep the majority of the community on recent versions of the framework for more than 8 years. He talks about lessons learned from the 1.13 upgrade, how the core team thinks about API experimentation vs. community fragmentation, and the approach Octane is taking to enable frontend developers that know HTML and CSS to ship interactive sites with Ember. Topics include:- 5:15 – What experiences led Ember to prioritize bringing the entire community along for upgrades and changes to the programming model- 21:22 – Why open source libraries shouldn't couple breaking changes to conceptual changes- 31:30 – How to think about the tradeoff between fragmentation and experimentation- 40:00 – How Ember is exposing more low-level primitives while still emphasizing its higher-level APIs- 45:01 – What mattered to Yehuda when he became a programmer, and how he's bringing that to the Ember community- 1:02:20 – Why Octane embraces HTML- 1:12:04 – What type of developer Octane targets- 1:24:22 – What the modern version of Rails' blog in 15 minutes could look like Links:- [Together: The Merb Story](https://yehudakatz.com/2020/02/19/together-the-merb-story/), Yehuda Katz- ["We're the Together Framework"](https://yehudakatz.com/2020/03/09/the-together-framework/), Yehuda Katz- [Coronavirus will also cause a loneliness epidemic](https://www.vox.com/2020/3/12/21173938/coronavirus-covid-19-social-distancing-elderly-epidemic-isolation-quarantine)

Topics include:- 0:00 - What is Faktory?- 2:28 – Why might I need a background job?- 13:26 – Why did you make Sidekiq?- 16:15 – What lead to Faktory?- 24:02 – Why'd you use Go to implement Faktory's server?- 25:36 – Who is Faktory for?- 31:58 – What's the most interesting thing you've learned about architecting background job systems?- 36:24 – How do you see job queuing work in a serverless world?- 41:23 – What are some of your thoughts on open source sustainability?- 46:48 – What makes a library productizable?- 48:30 – Were you thinking entrepreneurially when starting Sidekiq?- 53:30 – Could open source sustainability be solved by a marketplace or middleman?- 55:14 – How has your business model and financial incentives affected the development of your open source libraries?- 1:00:30 – How do you think about API additions and feature requests to Sidekiq? Links:- [Faktory](https://github.com/contribsys/faktory)- [Sidekiq](https://sidekiq.org)- [Mike on Twitter](https://twitter.com/getajobmike)- [Mike's blog](https://www.mikeperham.com)- [Building a $1 Million Business Solo with Mike Perham of Sidekiq](https://www.indiehackers.com/podcast/016-mike-perham-of-sidekiq)

Topics include:- 6:00 - Exploring Next.js's architecture- 22:33 - Is runtime SSR an antipattern?- 44:04 - Are there any downsides to this architecture?- 1:11:25 - React's single shot SSR vs. Ember's asynchronous FastBoot rendering Links:- [CAP theorem](https://en.wikipedia.org/wiki/CAP_theorem)- [Tweet from Guillermo: "Most use cases of SSR are better served by SSG"](https://twitter.com/rauchg/status/1226353359759634432)

Topics include:- 3:33 – Is usePrevious a bad hook?- 14:13 – Does declarative code make sense for app logic that's about state transitions, like animations?- 40:04 – Dependabot shifts some of the app maintenance burden from the app developer to the ops team. How might CI providers help solve these new devops issues?- 51:43 – GitHub actions Links:- [React Spring](https://www.react-spring.io)- [Framer Motion](https://www.framer.com/motion/)- [Dependabot](https://dependabot.com)- [GitHub Actions](https://github.com/features/actions)

Topics include:- 2:46 – Launching Mirage JS!- 10:17 – Feeling empowered bringing Mirage to the wider JS ecosystem, and what's next for Mirage- 19:40 – A Mirage tutorial + video series- 19:30 – GraphQL support in Mirage- 30:13 – TypeScript support in Mirage- 37:25 – Node support in Mirage Links:- [Mirage's new homepage](https://miragejs.com)

Topics include:- 4:45 - Building out Mirage's new homepage. SVG positioning.- 15:42 - CSS Grid for layouts- 19:36 - Update on launching Mirage JS. Adding types to Mirage.- 24:09 - Learning about idempotence through React Spring. What to do when UI isn't a function of state.- 52:40 - Sharp tools vs. high-level APIs Links:- [React Spring](https://www.react-spring.io)- [Small, Sharp Tools](https://brandur.org/small-sharp-tools)

Topics include:3:17 - Refactoring to Tailwind defaults11:17 - What exactly are Container components?17:35 - Marginless components23:40 - Grids25:50 - What you can learn by using Tailwind defaults41:00 - Using Mirage tests to re-create development scenarios50:45 - Frontend FirstLinks:Tailwind CSSReactiveConf 2019 - Mark Dalgleish: Rethinking Design PracticesFrontend First Development

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](https://vue-composition-api-rfc.netlify.com)- [MobX](https://mobx.js.org/README.html)