The Call Kent podcast is a regular podcast where you call in with a question and Kent answers. Call in with your questions right from your web browser with any ...
When is a Promise not good enough, and I need a Web Worker?
I just finished Expensive Calculations in React Performance. Why do we need a Web Worker instead of just wrapping the long-running function in a Promise that resolves when the function completes?
Expensive Calculations - Epic React Performance Workshop
When is a Promise not good enough, and I need a Web Worker?
--------
5:40
How Useful is LiteFS in 2025?
In 2022 you migrated a blog from postgres to LiteFS. Is that generally recommended in 2025?
How Useful is LiteFS in 2025?
--------
10:11
What are your thoughts about Qwik and hydration?
What do you think about resumability and Qwik? About 9 months ago, there was talk about Wiz and Angular working more closely together (Wiz was the tool that inspired Qwik). But Angular only committed to working on partial hydration support, not the full resumability like Qwik. So do you think React developers should care about this? If so, should they use partial hydration tools like Astro today or wait for something like resumability to be added to React?
𝕏 Post
What are your thoughts about Qwik and hydration?
--------
7:20
Dependent driven motivation and embracing AI
I would like to know how you get motivated knowing that you have dependents and stay strong in the event of layoff.
How do you handle the fear of AI taking over job?
My original post
Jyoti's response
P.S. I didn't really mention much about AI so feel free to ask a follow-up on this for a more specific answer, but I would say that AI is just an important tool we need to learn and keep using the best tools to get the best benefits. Check out this Epic Programming Principle: Adapt to and adopt productive tools
Dependent driven motivation and embracing AI
--------
7:43
Does the testing trophy need updating for 2025?
In 2024, we live in a world where the defacto for creating React applications is SSR (e.g. Remix, react router v7, Next, TanStack). Coupled with the rise in performance, reliability and reduction of cost in running e2e tests by playwright and now vitest's Browser Mode, is it time to consider reworking the Testing Trophy to make e2e tests the largest proportion of the trophy?
This is starting to make more and more sense to me as e2e tests are becoming as cheap to execute as integration tests, whilst integration tests are more complex to write in a SSR application without mocking client side or server side code.
The Testing Trophy and Testing Classifications
Vitest Browser Mode
@epic-web/app-launcher
Does the testing trophy need updating for 2025?
The Call Kent podcast is a regular podcast where you call in with a question and Kent answers. Call in with your questions right from your web browser with any device at https://kentcdodds.com/call
Österreich