10 years, and yet any discussion on this site about front-end development will be filled with people complaining about how front-end development practices change too quickly.
And that's only React, the ecosystem around it also has changed significantly.
https://web.archive.org/web/20130607112825/http://facebook.g...
Back in 2015, $JOB was evaluating upgrading Java 6 to Java 7 or 8. What is now? 20?
I last touched php in 2012, which was 5.4 or 5.5 I think. People were still arguing that Laravel couldn't replace CodeIgnitor, or that we should stick with Symphony or Zend.
Change is the only constant. In that respect, React has been relatively sane.
If you're a React developer, you'll have noticed that Javascript itself has changed a lot in ten years. The state management library your company uses has probably changed too. Compared to ten years ago, you're now writing fully-typed JS with Typescript. The additional libraries for authentication and persistence, and so on, have all changed as well. You may be using a graph-based database now. You may have a different JS runtime on the server. All of your tooling has probably changed, as has your IDE.
Whether React itself has or has not changed more than other frameworks, I can't say. But, I'd bet the stack used by the average front end developer has. Please recall that the original comment we're both talking about was referring to complaints about how much the front end has changed, with React only being the context of the comment, and not the sole cause of the complaint.
Ok then, what about the Spring .xml to .java migration? What about the Struts -> Struts2 -> SpringMVC -> SpringWebapp migrations.
It seems an unfair criticism of React.
When I started my first programming job 14 years ago xml was already not recommended and SpringMVC was already the way of doing things. So that's quite a bit stabler and slower than React.
And how much have you had to rewrite or replace going from 8 to 20? Very little, right?