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:

Mocking Complex APIs With Mirage JS

Mocking complex APIs with Mirage JS

Mock complex APIs with JavaScript’s Mirage JS library including JWT authentication, relational data, role-based access control, and more.

Emmanuel John
Apr 4, 2025 ⋅ 10 min read
8 best Go web frameworks for 2025

The 8 best Go web frameworks for 2025: Updated list

Looking for the best Go frameworks? Compare the top 8 Go web frameworks for 2025, including Gin, Fiber, Echo, and Beego, with pros, cons, and performance insights.

Victor Jonah
Apr 3, 2025 ⋅ 15 min read
Making Your First Game In Excalibur.js

Game development for frontend: Building with Excalibur.js

Build your first 2D browser game using JavaScript and the Excalibur.js library, covering essential game development concepts.

Yashodhan Joshi
Apr 3, 2025 ⋅ 25 min read
angular vs react

Angular vs. React: Which one should you choose?

Explore the key differences between Angular and React, their strengths, and use cases to help developers decide which option to choose.

Oscar Jite-Orimiono
Apr 2, 2025 ⋅ 5 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