4 ms·

Layoffs or no layoffs it is extremely unlikely React will be used as much as it is now 5-10 years from now. It will probably be legacy no one wants to touch any

Layoffs or no layoffs it is extremely unlikely React will be used as much as it is now 5-10 years from now. It will probably be legacy no one wants to touch anymore. That's the nature of front end development unfortunately. I hope to be proven wrong btw ...its about time we have a FE framework surviving more than 10 years.

quickthrower2 4y ago
I think React has made a deep impression in the industry and wont disappear overnight. There is less of a 'brainer' these days if you want to choose the boring tech for SPA (or similar) apps, and that is React.
kamaal 4y ago
Which framework do you think is the next big thing in the Frontend world?
- kethinov 4y ago
  I am hoping vanilla JS will some day replace all the frameworks as the core features the frameworks have get absorbed into web standards natively, like what happened to jQuery. It's already perfectly possible to build a modern SPA UX without frameworks but a lot of devs don't generally prefer it. Yet?
shishy 4y ago
react came out in 2013 so if it survives another year it'll be 10 years already; it's not going to disappear in the next year.
- weatherlite 4y ago
  Point taken you are right. So I wanna see a mainstream FE framework make it to 10 without completely changing its API (Angular, React hooks) or its state management (Redux, Mobix..what is next?) If you know Rails or Django fast forward 9 years.. you still know them. Can you say the same about React?
  - acemarke 4y ago
    For the record: I maintain Redux, and it's never been an actual recommendation from the React team. In fact, Dan has publicly stated that "the only state management tool we recommend is React itself". Redux is certainly the most widely _used_ state management lib in React apps, but that's a community-driven thing, not anything the React team has specifically suggested (in the same way that React Router is the most commonly used routing lib).
    - weatherlite 4y ago
      Oh no doubt. I am not blaming anyone specific here. I'm just calling it as it is - the way you write React apps now will be completely different 10 years from now.
  - reducesuffering 4y ago
    I think just frontend is a more apples to apples comparison. In that scope, what >10 teams >1m ARR are using plain Rails/Django html templates with html button actions and such? If you shop around at Rails/Django jobs, they're almost all going to be using different frontends that you'd need to ramp up on: React, Vue, jQuery, Hotwire, Turbo, Stimulus, HTMX, Alpine.js, etc. You could also say "If you know jQuery fast forward 9 years ago... you still know it" and be right about keeping yourself to the limited opportunities to do it the old-fashioned way.
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.
    - 4y ago
CuriouslyC 4y ago
JSX style templates and components aren't going anywhere. A new framework that handles context and events better than React by default might ascend, but a good portion of FE dev work will look the same.
- gardenhedge 4y ago
  yeah, tried angular again recently.. absolutely terrible dx

quickthrower2 4y ago

I think React has made a deep impression in the industry and wont disappear overnight. There is less of a 'brainer' these days if you want to choose the boring tech for SPA (or similar) apps, and that is React.

kamaal 4y ago

Which framework do you think is the next big thing in the Frontend world?

kethinov 4y ago
I am hoping vanilla JS will some day replace all the frameworks as the core features the frameworks have get absorbed into web standards natively, like what happened to jQuery. It's already perfectly possible to build a modern SPA UX without frameworks but a lot of devs don't generally prefer it. Yet?

shishy 4y ago

react came out in 2013 so if it survives another year it'll be 10 years already; it's not going to disappear in the next year.

weatherlite 4y ago
Point taken you are right. So I wanna see a mainstream FE framework make it to 10 without completely changing its API (Angular, React hooks) or its state management (Redux, Mobix..what is next?) If you know Rails or Django fast forward 9 years.. you still know them. Can you say the same about React?
- acemarke 4y ago
  For the record: I maintain Redux, and it's never been an actual recommendation from the React team. In fact, Dan has publicly stated that "the only state management tool we recommend is React itself". Redux is certainly the most widely _used_ state management lib in React apps, but that's a community-driven thing, not anything the React team has specifically suggested (in the same way that React Router is the most commonly used routing lib).
  - weatherlite 4y ago
    Oh no doubt. I am not blaming anyone specific here. I'm just calling it as it is - the way you write React apps now will be completely different 10 years from now.
- reducesuffering 4y ago
  I think just frontend is a more apples to apples comparison. In that scope, what >10 teams >1m ARR are using plain Rails/Django html templates with html button actions and such? If you shop around at Rails/Django jobs, they're almost all going to be using different frontends that you'd need to ramp up on: React, Vue, jQuery, Hotwire, Turbo, Stimulus, HTMX, Alpine.js, etc. You could also say "If you know jQuery fast forward 9 years ago... you still know it" and be right about keeping yourself to the limited opportunities to do it the old-fashioned way.

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.
  - 4y ago

CuriouslyC 4y ago

JSX style templates and components aren't going anywhere. A new framework that handles context and events better than React by default might ascend, but a good portion of FE dev work will look the same.

gardenhedge 4y ago
yeah, tried angular again recently.. absolutely terrible dx