301
Cloudflare DDoSed itself with React useEffect hook blunder
(www.theregister.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 18 Sep 2025
301 points (99.0% liked)
Technology
89461 readers
3538 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 3 years ago
MODERATORS
I recently ran a session and wrote an internal blog post about why useEffect was a dangerous crutch that should be avoided wherever possible. This was due to recently experienced over-complicated logic and unexpected interaction bugs.
This is a little different but I still feel vindicated.
You are correct, useEffect can be dangerous if you don't know exactly what you are doing. I would go so far as to say that most people use it incorrectly. This includes myself, I am not great at using React and end up using it in the wrong places, which according to a colleague, it should just be avoided if possible.