2021-05-24
3517
#react
Sebastian Weber
50000
May 24, 2021 ⋅ 12 min read

useState vs. useRef: Similarities, differences, and use cases

Sebastian Weber Fell in love with CSS and JS over 20 years ago.

Recent posts:

Fix over-caching with dynamic IO caching in Next.js 15

Next.js 15 caching overhaul: Fix overcaching with Dynamic IO and the use cache directive.

David Omotayo
Aug 6, 2025 ⋅ 10 min read
LLMs are facing a QA crisis here’s how we could solve it

LLMs are facing a QA crisis: Here’s how we could solve it

LLM QA isn’t just a tooling gap — it’s a fundamental shift in how we think about software reliability.

Rosario De Chiara
Aug 4, 2025 ⋅ 7 min read

Windsurf vs. Cursor: When to choose the challenger

Windsurf AI brings agentic coding and terminal control right into your IDE. We compare it to Cursor, explore its features, and build a real frontend project.

Chizaram Ken
Jul 31, 2025 ⋅ 9 min read

The CSS if() function: Conditional styling will never be the same

The CSS Working Group has approved the if() function for development, a feature that promises to bring true conditional styling directly to our stylesheets.

Ikeh Akinyemi
Jul 30, 2025 ⋅ 12 min read
View all posts

One Reply to "<code>useState</code> vs. <code>useRef</code>: Similarities, differences, and use cases"

  1. Don’t use:
    `App ${darkMode && “dark-mode”}`
    As it will result with an “App false” class, if dark mode is disabled.

    Instead, use:
    `App ${darkMode && “dark-mode” || “”}`
    or
    `App ${darkMode ? “dark-mode” : “”}`
    to generate “App ” as the class when dark mode is disabled.

Leave a Reply