What's been the primary driver of JavaScript adoption?

Frontend First

Apr 08, 2020•1 hr 7 min•Ep. 92

--:--

Listen in podcast apps:

Apple Podcasts

Spotify

Download

Listen to this episode in Metacast mobile app

Don't just listen to podcasts. Learn from them with transcripts, summaries, and chapters for every episode. Skim, search, and bookmark insights. Learn more

Episode description

Sam and Ryan discuss what has driven JavaScript adoption on the web over the past 5-10 years, and what implications those drivers have had for the tools and frameworks we work with today. They also talk about why it's still so hard to build good SPA experiences on the web.

Topics include:

- 5:10 – Finding real-world pain points

- 8:44 – Mirage Inspector's serverless backend

- 15:30 – Not being happy with our stack

- 18:38 – Why on SPAs on the web tend to be so awful?

- 30:37 – What has driven JS adoption?

- 45:42 - GraphQL vs Rails 5 years in

- 49:10 – SWR and a useResource hook

Links:

- [Tailwind CSS Tips, Tricks + Best Practices](https://www.youtube.com/watch?v=nqNIy8HkEQ8)

- [JavaScript Deployments with Brian LeRoux](https://softwareengineeringdaily.com/2020/03/04/javascript-deployments-with-brian-leroux/)

- [SWR, Zeit's data-fetching library for React](https://github.com/zeit/swr)

For the best experience, listen in Metacast app for iOS or Android