useEffect is for noobies
November 10, 2025 at 11:01 PM
useEffect is for noobies
Building a new dashboard or MVP? This video hilariously roasts React's complexity.
It perfectly explains the "just a library" dependency chaos and why `useEffect` was almost named `useFootGun`.
🎥 https://www.youtube.com/watch?v=HyWYpM_S-2c
It perfectly explains the "just a library" dependency chaos and why `useEffect` was almost named `useFootGun`.
🎥 https://www.youtube.com/watch?v=HyWYpM_S-2c
November 9, 2025 at 6:34 PM
Building a new dashboard or MVP? This video hilariously roasts React's complexity.
It perfectly explains the "just a library" dependency chaos and why `useEffect` was almost named `useFootGun`.
🎥 https://www.youtube.com/watch?v=HyWYpM_S-2c
It perfectly explains the "just a library" dependency chaos and why `useEffect` was almost named `useFootGun`.
🎥 https://www.youtube.com/watch?v=HyWYpM_S-2c
Just browsed through 65+ React interview questions and realised something: Everyone obsesses over useState & useEffect, but recruiters are increasingly asking about useMemo & useCallback!
Don't just learn the basics - optimisation is where you'll stand out.
Any other React tips to share? 🧠
Don't just learn the basics - optimisation is where you'll stand out.
Any other React tips to share? 🧠
November 9, 2025 at 4:05 PM
Just browsed through 65+ React interview questions and realised something: Everyone obsesses over useState & useEffect, but recruiters are increasingly asking about useMemo & useCallback!
Don't just learn the basics - optimisation is where you'll stand out.
Any other React tips to share? 🧠
Don't just learn the basics - optimisation is where you'll stand out.
Any other React tips to share? 🧠
<a href="https://zenn.dev/coji/scraps/c890994e6d42b4" class="hover:underline text-blue-600 dark:text-sky-400 no-card-link" target="_blank" rel="noopener" data-link="bsky">zenn.dev/coji/scraps/c8909...
コーディングエージェントが useEffect を多用するのがつらい
コーディングエージェントが useEffect を多用するのがつらい
コーディングエージェントが useEffect を多用するのがつらい
zenn.dev
November 9, 2025 at 11:46 AM
<a href="https://zenn.dev/coji/scraps/c890994e6d42b4" class="hover:underline text-blue-600 dark:text-sky-400 no-card-link" target="_blank" rel="noopener" data-link="bsky">zenn.dev/coji/scraps/c8909...
コーディングエージェントが useEffect を多用するのがつらい
コーディングエージェントが useEffect を多用するのがつらい
React 19.2 was released Oct. 1! It's a month old and here you go!
useEffectEvent - Allows you to have a dependent that doesn't trigger the useEffect
Activity API -This is a great wrapper that take the place of {boolean &&<MyComponent />}
allowing you to hide components w/o destroying their state.
useEffectEvent - Allows you to have a dependent that doesn't trigger the useEffect
Activity API -This is a great wrapper that take the place of {boolean &&<MyComponent />}
allowing you to hide components w/o destroying their state.
November 8, 2025 at 2:52 PM
React 19.2 was released Oct. 1! It's a month old and here you go!
useEffectEvent - Allows you to have a dependent that doesn't trigger the useEffect
Activity API -This is a great wrapper that take the place of {boolean &&<MyComponent />}
allowing you to hide components w/o destroying their state.
useEffectEvent - Allows you to have a dependent that doesn't trigger the useEffect
Activity API -This is a great wrapper that take the place of {boolean &&<MyComponent />}
allowing you to hide components w/o destroying their state.
Also tapping into existing vanilla JS libraries is easier in Svelte than React. Particularly where set up involves append to an element (eg three.js, D3.js ). onMount does not have the quirks of useEffect such as the double rendering of components on dev but not production when React.strict is on.
November 8, 2025 at 10:19 AM
Also tapping into existing vanilla JS libraries is easier in Svelte than React. Particularly where set up involves append to an element (eg three.js, D3.js ). onMount does not have the quirks of useEffect such as the double rendering of components on dev but not production when React.strict is on.
https://zenn.dev/coji/scraps/c890994e6d42b4
useEffect の使用に関するルールをまとめたドキュメントです。
API呼び出しやWebSocket接続など、外部との同期にのみ使用すべきとされています。
props のコピーやイベントハンドラ以外のロジックでの使用はアンチパターンです。
useEffect の使用に関するルールをまとめたドキュメントです。
API呼び出しやWebSocket接続など、外部との同期にのみ使用すべきとされています。
props のコピーやイベントハンドラ以外のロジックでの使用はアンチパターンです。
コーディングエージェントが useEffect を多用するのがつらい
Coji Mizoguchiさんのスクラップ
zenn.dev
November 8, 2025 at 2:41 AM
https://zenn.dev/coji/scraps/c890994e6d42b4
useEffect の使用に関するルールをまとめたドキュメントです。
API呼び出しやWebSocket接続など、外部との同期にのみ使用すべきとされています。
props のコピーやイベントハンドラ以外のロジックでの使用はアンチパターンです。
useEffect の使用に関するルールをまとめたドキュメントです。
API呼び出しやWebSocket接続など、外部との同期にのみ使用すべきとされています。
props のコピーやイベントハンドラ以外のロジックでの使用はアンチパターンです。
コーディングエージェントが useEffect を多用するのがつらい
https://zenn.dev/coji/scraps/c890994e6d42b4
https://zenn.dev/coji/scraps/c890994e6d42b4
コーディングエージェントが useEffect を多用するのがつらい
Coji Mizoguchiさんのスクラップ
zenn.dev
November 7, 2025 at 11:04 PM
コーディングエージェントが useEffect を多用するのがつらい
https://zenn.dev/coji/scraps/c890994e6d42b4
https://zenn.dev/coji/scraps/c890994e6d42b4
A Practical Guide to React Suspense and Lazy Loading Fetching data and loading components in React has traditionally revolved around the useEffect and useState hooks, requiring manual… The post A...
#Software #beginner #prodsens #live #programming #react #webdev
Origin | Interest | Match
#Software #beginner #prodsens #live #programming #react #webdev
Origin | Interest | Match
A Practical Guide to React Suspense and Lazy Loading - prodSens.live
Fetching data and loading components in React has traditionally revolved around the useEffect and useState hooks, requiring manual…
prodsens.live
November 7, 2025 at 7:01 AM
A Practical Guide to React Suspense and Lazy Loading Fetching data and loading components in React has traditionally revolved around the useEffect and useState hooks, requiring manual… The post A...
#Software #beginner #prodsens #live #programming #react #webdev
Origin | Interest | Match
#Software #beginner #prodsens #live #programming #react #webdev
Origin | Interest | Match
A Practical Guide to React Suspense and Lazy Loading - prodSens.live
Fetching data and loading components in React has traditionally revolved around the useEffect and useState hooks, requiring manual…
prodsens.live
November 7, 2025 at 4:50 AM
A Practical Guide to React Suspense and Lazy Loading Fetching data and loading components in React has traditionally revolved around the useEffect and useState hooks, requiring manual management of...
#react #webdev #programming #beginner
Origin | Interest | Match
#react #webdev #programming #beginner
Origin | Interest | Match
A Practical Guide to React Suspense and Lazy Loading
Fetching data and loading components in React has traditionally revolved around the useEffect and...
dev.to
November 7, 2025 at 4:17 AM
This is fair and square. Though I rather wanted to emphasise that you don’t need to fail or have any problem to dislike useeffect.
November 6, 2025 at 10:35 PM
This is fair and square. Though I rather wanted to emphasise that you don’t need to fail or have any problem to dislike useeffect.
Using a second comparative state is still not very intuitive today, but before batched updates, it also created extra re-renders
Before useEffectEvent, useRef + useEffect was the only way to use functions with unstable references in another useEffect
Optimistic state, asynchronous state, and so on
Before useEffectEvent, useRef + useEffect was the only way to use functions with unstable references in another useEffect
Optimistic state, asynchronous state, and so on
November 6, 2025 at 10:10 PM
Using a second comparative state is still not very intuitive today, but before batched updates, it also created extra re-renders
Before useEffectEvent, useRef + useEffect was the only way to use functions with unstable references in another useEffect
Optimistic state, asynchronous state, and so on
Before useEffectEvent, useRef + useEffect was the only way to use functions with unstable references in another useEffect
Optimistic state, asynchronous state, and so on
In the case of React, there's also the historical factor that for a long time, useEffect was the only way to achieve many things
Before useSyncExternalStore, it was the only way to sync with external state
Before useSyncExternalStore, it was the only way to sync with external state
November 6, 2025 at 10:10 PM
In the case of React, there's also the historical factor that for a long time, useEffect was the only way to achieve many things
Before useSyncExternalStore, it was the only way to sync with external state
Before useSyncExternalStore, it was the only way to sync with external state
If the real problem is too many usestate, how come solid has separate createffect, onmount and oncleanup without the need of declaring a dependency array?
I don’t think one need to fail in any way to dislike useeffect.
I don’t think one need to fail in any way to dislike useeffect.
November 6, 2025 at 9:05 PM
If the real problem is too many usestate, how come solid has separate createffect, onmount and oncleanup without the need of declaring a dependency array?
I don’t think one need to fail in any way to dislike useeffect.
I don’t think one need to fail in any way to dislike useeffect.
I think useEffect gets a bad rep because of the re-rendering model
In any framework, changing state within an effect is suboptimal
In React, even when it doesn't create an infinite loop, it's still a ticking time bomb waiting to explode your app's performance by creating additional rendering cycles.
In any framework, changing state within an effect is suboptimal
In React, even when it doesn't create an infinite loop, it's still a ticking time bomb waiting to explode your app's performance by creating additional rendering cycles.
November 6, 2025 at 7:03 PM
I think useEffect gets a bad rep because of the re-rendering model
In any framework, changing state within an effect is suboptimal
In React, even when it doesn't create an infinite loop, it's still a ticking time bomb waiting to explode your app's performance by creating additional rendering cycles.
In any framework, changing state within an effect is suboptimal
In React, even when it doesn't create an infinite loop, it's still a ticking time bomb waiting to explode your app's performance by creating additional rendering cycles.
If it didn't need to exist it wouldn't. But it does. It is too easy to blame `useEffect` itself to be the square hole. Yes Hammers exist. While it is easy to blame the design, what we need is to be able to identify why this happens. So we can encourage better patterns.
bsky.app/profile/seba...
bsky.app/profile/seba...
The React core team when they see devs using useEffect
November 6, 2025 at 5:31 PM
If it didn't need to exist it wouldn't. But it does. It is too easy to blame `useEffect` itself to be the square hole. Yes Hammers exist. While it is easy to blame the design, what we need is to be able to identify why this happens. So we can encourage better patterns.
bsky.app/profile/seba...
bsky.app/profile/seba...
Ryan defending useEffect, didn't see this coming!
November 6, 2025 at 5:20 PM
Ryan defending useEffect, didn't see this coming!
People give `useEffect` a bad rap, but it isn't usually the source of the problem. The real problem is too many `useState`s.
Devs fail to see how their data is connected and model it too discretely. As those connections appear, it is easier to synchronize than refactor the model. 1/
Devs fail to see how their data is connected and model it too discretely. As those connections appear, it is easier to synchronize than refactor the model. 1/
November 6, 2025 at 4:41 PM
People give `useEffect` a bad rap, but it isn't usually the source of the problem. The real problem is too many `useState`s.
Devs fail to see how their data is connected and model it too discretely. As those connections appear, it is easier to synchronize than refactor the model. 1/
Devs fail to see how their data is connected and model it too discretely. As those connections appear, it is easier to synchronize than refactor the model. 1/
react19 なのに useEffect ばっかでなんだかなあという気持ち use 使いたい
かといってリンターで厳しくしまくったり、AGENETS.md を増やしまくったら開発体験落ちるだろうし悩ましい
AI の成熟待つしかないのかなあ
かといってリンターで厳しくしまくったり、AGENETS.md を増やしまくったら開発体験落ちるだろうし悩ましい
AI の成熟待つしかないのかなあ
November 6, 2025 at 1:24 PM
react19 なのに useEffect ばっかでなんだかなあという気持ち use 使いたい
かといってリンターで厳しくしまくったり、AGENETS.md を増やしまくったら開発体験落ちるだろうし悩ましい
AI の成熟待つしかないのかなあ
かといってリンターで厳しくしまくったり、AGENETS.md を増やしまくったら開発体験落ちるだろうし悩ましい
AI の成熟待つしかないのかなあ
The React core team when they see devs using useEffect
November 5, 2025 at 11:29 AM
The React core team when they see devs using useEffect
can we kill everyone who does `import * as React from "react-dom"` instead of `import { useEffect } from "react-dom"`
November 4, 2025 at 10:22 PM
can we kill everyone who does `import * as React from "react-dom"` instead of `import { useEffect } from "react-dom"`
Which is unfortunate because that isn't what React was talking about. They don't want you making render loops in React either. The reason unidirectional is important is to prevent mid-cycle glitches. Places where the UI can see intermediate values. But writing to state in useEffect does that too.
November 4, 2025 at 5:12 PM
Which is unfortunate because that isn't what React was talking about. They don't want you making render loops in React either. The reason unidirectional is important is to prevent mid-cycle glitches. Places where the UI can see intermediate values. But writing to state in useEffect does that too.
That's like saying `useEffect` writing state it depends on causes a reactivity loop. I mean it does, but why would anyone do that intentionally? In the same way don't write to signals during pure computations. Anything that loops in Solid would loop in React.
November 4, 2025 at 4:33 PM
That's like saying `useEffect` writing state it depends on causes a reactivity loop. I mean it does, but why would anyone do that intentionally? In the same way don't write to signals during pure computations. Anything that loops in Solid would loop in React.