Frontend First

Is Suspense “backwards compatible”, and thoughts on Remix & web standards

Jan 29, 2022

01:03:41

Creator website

Highlights

AI Chapters

Episode notes

Is There a Suspense World?

02:13

Web Standards

02:23

Suspense Cleans Up Effects

01:41

Introduction

2min

Is User a Monkey?

4min

Getting the Initial Ostate From Fire Base

2min

How to Get a Component to Suspend During Fetching?

2min

Is Ridy Thais Ye?

2min

A Suspense Enabled Component Doesn't Compile Well

3min

Is There a Way to Split Out the Effects?

2min

Suspense Cleans Up Effects

2min

Can a React App Really Be Rendered?

2min

10.

How to Add Guards to Effects

4min

11.

Set Up Analytics - Is Your Fat Code Like Tracking?

2min

12.

Is There a Suspense World?

2min

13.

I Think It Will Affect the Way We Write Coding

2min

14.

Is Suspense Ready?

3min

15.

Rails - The Most Important Thing About Rails

3min

16.

Rails Abstractions - Is That What You're Saying?

2min

17.

Building a Webap

2min

18.

Web Standards

2min

19.

Web Standards Matter to Framework Authors

4min

20.

Remix Has a Form Component That Does a Lot of Stuff for You

3min

21.

Web Standards Matter, Right?

3min

22.

Is There a Better Way to Do It?

2min

23.

Is Your Framework a React?

2min

24.

Is It a Good Idea to Build a Rail Zap?

2min

25.

Pick React in S P A

2min

26.

The Curse to React

3min

Sam and Ryan chat about how Suspense lets you remove defensive and confusing useEffect code from your React components. They also share some initial thoughts about how Remix is positioning itself in the frontend dev space.

Topics include:

0:00 - Intro
4:53 - How compatible are non-Suspense APIs with Suspense, and how can we bridge these two worlds?
33:35 - Impressions about Remix’s positioning around web standards

Links:

Remember Everything You Learn from Podcasts

Save insights instantly, chat with episodes, and build lasting knowledge - all powered by AI.