2019-04-02
825
#react
Oliver Williams
104
Apr 2, 2019 ⋅ 2 min read

Making the business case for React in 2019

Oliver Williams Frontend developer at Suntory.

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 "Making the business case for React in 2019"

  1. You can’t compare market share and # of download of a library. React is used by high traffic websites with a large dev groups that work on the project all the time. That drives downloads on NPM. But it has nothing to do with market share. The actual data shows market share is 0.3% (April 2020) https://w3techs.com/technologies/details/js-react

Leave a Reply