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:

the replay december 17

The Replay (12/17/25): React2Shell, Shopify Winter ‘26, and more

Discover what’s new in The Replay, LogRocket’s newsletter for dev and engineering leaders, in the December 17th issue.

Matt MacCormack
Dec 17, 2025 ⋅ 34 sec read
react 2 shell vulnerability shruti kapoor

React2Shell exploit: What happened and lessons learned

Shruti Kapoor breaks down the React2Shell exploit and discusses lessons that dev teams can take away from one of the biggest security events of the year.

Shruti Kapoor
Dec 17, 2025 ⋅ 6 min read
Angular Vs. React Vs. Vue.js: Comparing Performance

Angular vs. React vs. Vue.js: A performance guide for 2026

React, Angular, and Vue still lead frontend development, but 2025 performance is shaped by signals, compilers, and hydration. Here’s how they compare.

Nefe Emadamerho-Atori
Dec 16, 2025 ⋅ 19 min read

Drizzle and React Native (Expo): Local SQLite setup

Learn how to use Drizzle ORM with Expo SQLite in a React Native app, including schema setup, migrations, and type-safe queries powered by TanStack Query.

Nitish Sharma
Dec 16, 2025 ⋅ 6 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

Hey there, want to help make our blog better?

Join LogRocket’s Content Advisory Board. You’ll help inform the type of content we create and get access to exclusive meetups, social accreditation, and swag.

Sign up now