Why React JS? | Call Kent Podcast | 42

Calls with Kent C. Dodds.

You call, I'll answer.

Record your call

Listen to the podcasts here

Apple podcasts Pocket Casts

Phone sitting on a stool

What's this all about?

The goal of the Call Kent Podcast is to get my answers to your questions. You record your brief question (120 seconds or less) right from your browser. Then I listen to it later and give my response, and through the magic of technology (ffmpeg), our question and answer are stitched together and published to the podcast feed.

I look forward to hearing from you!

Record your call

Calls with Kent C. Dodds Season 1 — 50 episodes

50.How to decide among advanced react patterns?

49.Handling difficult co-workers and/or leadership

48.Use React frameworks (Remix) for SPAs

47.Isolating tests

46.Versioning and dependency management for libraries

45.Full stack framework vs front-end with saas

44.Learning Gaps & Cluelessness as a Developer

43.Alfred and/or ScriptKit?

42.Why React JS?

Keywords

reactjs, double-edged, sword

Description

We're observing a lot of feedback about React and started to think "why". Why not Svetle or Vue? Why not something else.

And it's also inspired by what you have put on the epicreact.dev landing page about why React is awesome.

One of the good examples for more context please read: https://dev.to/jfbrennan/really-why-react-5958

41.Bailing out of re-rendering in useState

40.Remix Styling w/CSS in JS

39.Learning web development the right way

38.Testing a Drag and Drop Experience

37.Protected route and redirect after payment

36.Making changes on a new team

35.Building an Open Source Website

34.Question about testing alongside RTL

33.Create web components in React

32.Magic links require timely email delivery

31.Some advice for developers about the design

30.Pricing low-demand workshops

28.Forms in React

27.How small should components be

26.Using Fly.io Replays

25.Why is forwardRef required to limit re-renders?

24.Traditional logins vs. passwordless magic links

23.How to plan curriculum

22.Why Remix over other React frameworks?

21.What did paypal-scripts do?

20.What are your thoughts on Svelte?

19.Where did those diagrams come from?

18.Filling CS concept holes as a non-CS major?

17.How to buy for EpicReact in "installments"

16.Best approach for building headless components

15.Cypress Component Testing Library vs Jest

14.How does Remix manage many CSS files in a page?

13.Mirage JS over MSW?

12.Work Life Balance

11.How much of seniority is about code skills?

09.How to style?

07.Managing Burnout

06.Make It Stick: Interleave Curves

05.What is the best way to go through EpicReact?

04.How do you find new technology

03.Difference in methods emanating from screen and render

02.Dealing with "act" warning on react testing

01.Reusing components between different projects

50.How to decide among advanced react patterns?

49.Handling difficult co-workers and/or leadership

48.Use React frameworks (Remix) for SPAs

47.Isolating tests

46.Versioning and dependency management for libraries

45.Full stack framework vs front-end with saas

44.Learning Gaps & Cluelessness as a Developer

43.Alfred and/or ScriptKit?

42.Why React JS?

Keywords

reactjs, double-edged, sword

Description

We're observing a lot of feedback about React and started to think "why". Why not Svetle or Vue? Why not something else.

And it's also inspired by what you have put on the epicreact.dev landing page about why React is awesome.

One of the good examples for more context please read: https://dev.to/jfbrennan/really-why-react-5958

41.Bailing out of re-rendering in useState

40.Remix Styling w/CSS in JS

39.Learning web development the right way

38.Testing a Drag and Drop Experience

37.Protected route and redirect after payment

36.Making changes on a new team

35.Building an Open Source Website

34.Question about testing alongside RTL

33.Create web components in React

32.Magic links require timely email delivery

31.Some advice for developers about the design

30.Pricing low-demand workshops

28.Forms in React

27.How small should components be

26.Using Fly.io Replays

25.Why is forwardRef required to limit re-renders?

24.Traditional logins vs. passwordless magic links

23.How to plan curriculum

22.Why Remix over other React frameworks?

21.What did paypal-scripts do?

20.What are your thoughts on Svelte?

19.Where did those diagrams come from?

18.Filling CS concept holes as a non-CS major?

17.How to buy for EpicReact in "installments"

16.Best approach for building headless components

15.Cypress Component Testing Library vs Jest

14.How does Remix manage many CSS files in a page?

13.Mirage JS over MSW?

12.Work Life Balance

11.How much of seniority is about code skills?

09.How to style?

07.Managing Burnout

06.Make It Stick: Interleave Curves

05.What is the best way to go through EpicReact?

04.How do you find new technology

03.Difference in methods emanating from screen and render

02.Dealing with "act" warning on react testing

01.Reusing components between different projects

50.How to decide among advanced react patterns?

49.Handling difficult co-workers and/or leadership

48.Use React frameworks (Remix) for SPAs

47.Isolating tests

46.Versioning and dependency management for libraries

45.Full stack framework vs front-end with saas

44.Learning Gaps & Cluelessness as a Developer

43.Alfred and/or ScriptKit?

42.Why React JS?

Keywords

reactjs, double-edged, sword

Description

We're observing a lot of feedback about React and started to think "why". Why not Svetle or Vue? Why not something else.

And it's also inspired by what you have put on the epicreact.dev landing page about why React is awesome.

One of the good examples for more context please read: https://dev.to/jfbrennan/really-why-react-5958

41.Bailing out of re-rendering in useState

40.Remix Styling w/CSS in JS

39.Learning web development the right way

38.Testing a Drag and Drop Experience

37.Protected route and redirect after payment

36.Making changes on a new team

35.Building an Open Source Website

34.Question about testing alongside RTL

33.Create web components in React

32.Magic links require timely email delivery

31.Some advice for developers about the design

30.Pricing low-demand workshops

28.Forms in React

27.How small should components be

26.Using Fly.io Replays

25.Why is forwardRef required to limit re-renders?

24.Traditional logins vs. passwordless magic links

23.How to plan curriculum

22.Why Remix over other React frameworks?

21.What did paypal-scripts do?

20.What are your thoughts on Svelte?

19.Where did those diagrams come from?

18.Filling CS concept holes as a non-CS major?

17.How to buy for EpicReact in "installments"

16.Best approach for building headless components

15.Cypress Component Testing Library vs Jest

14.How does Remix manage many CSS files in a page?

13.Mirage JS over MSW?

12.Work Life Balance

11.How much of seniority is about code skills?

09.How to style?

07.Managing Burnout

06.Make It Stick: Interleave Curves

05.What is the best way to go through EpicReact?

04.How do you find new technology

03.Difference in methods emanating from screen and render

02.Dealing with "act" warning on react testing

01.Reusing components between different projects

50.How to decide among advanced react patterns?

49.Handling difficult co-workers and/or leadership

48.Use React frameworks (Remix) for SPAs

47.Isolating tests

46.Versioning and dependency management for libraries

45.Full stack framework vs front-end with saas

44.Learning Gaps & Cluelessness as a Developer

43.Alfred and/or ScriptKit?

42.Why React JS?

Keywords

reactjs, double-edged, sword

Description

We're observing a lot of feedback about React and started to think "why". Why not Svetle or Vue? Why not something else.

And it's also inspired by what you have put on the epicreact.dev landing page about why React is awesome.

One of the good examples for more context please read: https://dev.to/jfbrennan/really-why-react-5958

41.Bailing out of re-rendering in useState

40.Remix Styling w/CSS in JS

39.Learning web development the right way

38.Testing a Drag and Drop Experience

37.Protected route and redirect after payment

36.Making changes on a new team

35.Building an Open Source Website

34.Question about testing alongside RTL

33.Create web components in React

32.Magic links require timely email delivery

31.Some advice for developers about the design

30.Pricing low-demand workshops

28.Forms in React

27.How small should components be

26.Using Fly.io Replays

25.Why is forwardRef required to limit re-renders?

24.Traditional logins vs. passwordless magic links

23.How to plan curriculum

22.Why Remix over other React frameworks?

21.What did paypal-scripts do?

20.What are your thoughts on Svelte?

19.Where did those diagrams come from?

18.Filling CS concept holes as a non-CS major?

17.How to buy for EpicReact in "installments"

16.Best approach for building headless components

15.Cypress Component Testing Library vs Jest

14.How does Remix manage many CSS files in a page?

13.Mirage JS over MSW?

12.Work Life Balance

11.How much of seniority is about code skills?

09.How to style?

07.Managing Burnout

06.Make It Stick: Interleave Curves

05.What is the best way to go through EpicReact?

04.How do you find new technology

03.Difference in methods emanating from screen and render

02.Dealing with "act" warning on react testing

01.Reusing components between different projects

50.How to decide among advanced react patterns?

49.Handling difficult co-workers and/or leadership

48.Use React frameworks (Remix) for SPAs

47.Isolating tests

46.Versioning and dependency management for libraries

45.Full stack framework vs front-end with saas

44.Learning Gaps & Cluelessness as a Developer

43.Alfred and/or ScriptKit?

42.Why React JS?

Keywords

reactjs, double-edged, sword

Description

We're observing a lot of feedback about React and started to think "why". Why not Svetle or Vue? Why not something else.

And it's also inspired by what you have put on the epicreact.dev landing page about why React is awesome.

One of the good examples for more context please read: https://dev.to/jfbrennan/really-why-react-5958

41.Bailing out of re-rendering in useState

40.Remix Styling w/CSS in JS

39.Learning web development the right way

38.Testing a Drag and Drop Experience

37.Protected route and redirect after payment

36.Making changes on a new team

35.Building an Open Source Website

34.Question about testing alongside RTL

33.Create web components in React

32.Magic links require timely email delivery

31.Some advice for developers about the design

30.Pricing low-demand workshops

28.Forms in React

27.How small should components be

26.Using Fly.io Replays

25.Why is forwardRef required to limit re-renders?

24.Traditional logins vs. passwordless magic links

23.How to plan curriculum

22.Why Remix over other React frameworks?

21.What did paypal-scripts do?

20.What are your thoughts on Svelte?

19.Where did those diagrams come from?

18.Filling CS concept holes as a non-CS major?

17.How to buy for EpicReact in "installments"

16.Best approach for building headless components

15.Cypress Component Testing Library vs Jest

14.How does Remix manage many CSS files in a page?

13.Mirage JS over MSW?

12.Work Life Balance

11.How much of seniority is about code skills?

09.How to style?

07.Managing Burnout

06.Make It Stick: Interleave Curves

05.What is the best way to go through EpicReact?

04.How do you find new technology

03.Difference in methods emanating from screen and render

02.Dealing with "act" warning on react testing

01.Reusing components between different projects

Looking for more content?

Have a look at these articles.

See the full blog

by Jordan Whitt

by Jordan Whitt

May 11th, 2021 — 10 min read

Don't Solve Problems, Eliminate Them

by rawpixel

August 17th, 2020 — 12 min read

Testing Implementation Details

by Mohamed Nohassi

by Mohamed Nohassi

December 1st, 2020 — 3 min read

useEffect vs useLayoutEffect