4 ms·

React is already almost 10y old. Just check framework usage and downloads, stackoverflow survey etc. React just keep rising, exponentially. Vue had major growth

by mirzap 4y ago

React is already almost 10y old. Just check framework usage and downloads, stackoverflow survey etc. React just keep rising, exponentially. Vue had major growth couple of years ago, but it flatlined since then. TBH I don't see React going anywhere in the next 10y. It's like Java of frontened world. You think it's not there, but it's everywhere.

WA 4y ago
Replace React with jQuery in your post, see what happens.
- twelve40 4y ago
  jQuery (2006) was unseated by specific things like Angular (2010), Ember (2011) and then React (2013). What is taking over React currently? Vue?
  - Emigre_ 4y ago
    And Backbone.js (2010).
  - Macha 4y ago
    And certainly in 2012, both Angular.js and Ember used jQuery as an integral part of their implementation and even exposed it directly to users in their directive/Ember.$ APIs, so the actual end of widespread jQuery in new projects was later than that.
- javchz 4y ago
  I'll say the death of JQuery rather than being replaced by React or Angular, was more a result of standardization of ECMAScript and the progress of native APIs in browsers. Before JQuery creating your own JS for a weird IE6 bug was a nightmare; but with that problem solved in the modern web development, JQuery killer feature became a little redundant. I seriously doubt "native web components" or something similar will catch in the same momentum to kill React.
  - ipaddr 4y ago
    The number of people who went from jQuery to native is much much lower than you mention. Most moved to angular/react/vue/some framework. People replaced jQuery to handle state easier not because of standardization..
    - courgette 4y ago
      Idk I’m not a front end guy but I mostly stopped to reach for jquery as much. Standard stuff are sufficient ( for simple site and POC )
- mirzap 4y ago
  React keeps evolving, following technological progress, inventing new approaches to make frontend development easier. As other comment pointed out, React today is not the same as React 5y ago and it will not be the same 5y from now. jQuery is the same as jQuery 5y ago. Java is not the same as Java 10y ago, it kept evolving. That's why is still strong and alive. That's why React is here. That's why jQuery is not.
weatherlite 4y ago
It might be still called React but will be completely different. How similar are React + hooks + redux to React of 4 years ago? We call both React but it's hardly similar. Fast forward 10 years from now...
- reducesuffering 4y ago
  True, however even redux is on its way out. Dan Abramov, the creator, doesn't particularly recommend it anymore. Now, you'll see more React-Query and into the future: use() hook and SSC (Server Side Components)
  - acemarke 4y ago
    FWIW, my estimates show that Redux is still used by 35-40% of React apps [0]. That's definitely less than it was a couple years ago, but still the largest usage of any React-related state lib by far. (It's also worth noting that Dan stopped working on Redux in 2016 after one year and handed it over to Tim Dorr, myself, and now Lenz Weber, and has not been involved with Redux since then.) On the flip side, usage of our modern Redux Toolkit package continues to go up fairly rapidly (to the point that RTK by itself is more widely used than other libs like Mobx or Zustand), and we get tons of positive feedback daily from folks who enjoy using it. Also, Redux Toolkit's "RTK Query" data fetching and caching API also addresses the same use case as React Query, with some unique features and capabilities (OpenAPI/GraphQL codegen, streaming updates, cache lifecycles) [1]. So, while Redux will never be the "must-have" it was in 2016-17, it's still an excellent choice in many cases, and still very widely used. [0] https://blog.isquaredsoftware.com/2022/07/npm-package-market-share-estimates/ https://blog.isquaredsoftware.com/2022/07/npm-package-market... [1] https://redux-toolkit.js.org/rtk-query/comparison https://redux-toolkit.js.org/rtk-query/comparison
GGO 4y ago
It's a pity Vue is not getting more love and attention. I enjoyed working with it and seemed very promising.
- ilrwbwrkhv 4y ago
  Then they copied React and went with hooks and use this and use that and all that nonsense. One might argue they also copied angular 1 initially so they have no original ideas.

by mirzap 4y ago

WA 4y ago

Replace React with jQuery in your post, see what happens.

twelve40 4y ago
jQuery (2006) was unseated by specific things like Angular (2010), Ember (2011) and then React (2013). What is taking over React currently? Vue?
- Emigre_ 4y ago
  And Backbone.js (2010).
- Macha 4y ago
  And certainly in 2012, both Angular.js and Ember used jQuery as an integral part of their implementation and even exposed it directly to users in their directive/Ember.$ APIs, so the actual end of widespread jQuery in new projects was later than that.
javchz 4y ago
I'll say the death of JQuery rather than being replaced by React or Angular, was more a result of standardization of ECMAScript and the progress of native APIs in browsers. Before JQuery creating your own JS for a weird IE6 bug was a nightmare; but with that problem solved in the modern web development, JQuery killer feature became a little redundant. I seriously doubt "native web components" or something similar will catch in the same momentum to kill React.
- ipaddr 4y ago
  The number of people who went from jQuery to native is much much lower than you mention. Most moved to angular/react/vue/some framework. People replaced jQuery to handle state easier not because of standardization..
  - courgette 4y ago
    Idk I’m not a front end guy but I mostly stopped to reach for jquery as much. Standard stuff are sufficient ( for simple site and POC )
mirzap 4y ago
React keeps evolving, following technological progress, inventing new approaches to make frontend development easier. As other comment pointed out, React today is not the same as React 5y ago and it will not be the same 5y from now. jQuery is the same as jQuery 5y ago. Java is not the same as Java 10y ago, it kept evolving. That's why is still strong and alive. That's why React is here. That's why jQuery is not.

weatherlite 4y ago

It might be still called React but will be completely different. How similar are React + hooks + redux to React of 4 years ago? We call both React but it's hardly similar. Fast forward 10 years from now...

reducesuffering 4y ago
True, however even redux is on its way out. Dan Abramov, the creator, doesn't particularly recommend it anymore. Now, you'll see more React-Query and into the future: use() hook and SSC (Server Side Components)
- acemarke 4y ago
  FWIW, my estimates show that Redux is still used by 35-40% of React apps [0]. That's definitely less than it was a couple years ago, but still the largest usage of any React-related state lib by far. (It's also worth noting that Dan stopped working on Redux in 2016 after one year and handed it over to Tim Dorr, myself, and now Lenz Weber, and has not been involved with Redux since then.) On the flip side, usage of our modern Redux Toolkit package continues to go up fairly rapidly (to the point that RTK by itself is more widely used than other libs like Mobx or Zustand), and we get tons of positive feedback daily from folks who enjoy using it. Also, Redux Toolkit's "RTK Query" data fetching and caching API also addresses the same use case as React Query, with some unique features and capabilities (OpenAPI/GraphQL codegen, streaming updates, cache lifecycles) [1]. So, while Redux will never be the "must-have" it was in 2016-17, it's still an excellent choice in many cases, and still very widely used. [0] https://blog.isquaredsoftware.com/2022/07/npm-package-market-share-estimates/ https://blog.isquaredsoftware.com/2022/07/npm-package-market... [1] https://redux-toolkit.js.org/rtk-query/comparison https://redux-toolkit.js.org/rtk-query/comparison

GGO 4y ago

It's a pity Vue is not getting more love and attention. I enjoyed working with it and seemed very promising.

ilrwbwrkhv 4y ago
Then they copied React and went with hooks and use this and use that and all that nonsense. One might argue they also copied angular 1 initially so they have no original ideas.