3 ms·

> It’s way worse than React in this regard (if not only by its sheer size and larger scope) FWIW, I've used React for 18 months now. Except Java and classic co

> It’s way worse than React in this regard (if not only by its sheer size and larger scope) FWIW, I've used React for 18 months now. Except Java and classic core PHP it is one of the most stable platforms I've developed on. So, in my view being less stable than React isn't a big problem.

3np 5y ago
Yeah, I'm talking about having used React extensively since its inception 8 years ago with a couple of 1-3 years periods of being out of that ecosystem and coming back again. I'm sure it's a completely different game these days. Especially I recall that with lifecycle methods, previously idiomatic patterns would be deprecated with stern runtime warning within a year. Like this: https://reactjs.org/blog/2018/03/27/update-on-async-rendering.html https://reactjs.org/blog/2018/03/27/update-on-async-renderin... Granted React team has been way more effective at communicating than the .NET team, again facilitated by a much smaller scope. As for the ecosystem: Anyone else remembers when react-saga was The One Way To Manage Effects? Or going through all the major versions of react-router?
kqr 5y ago
I agree, React itself can be remarkably stable because they found the right abstractions early on and have been able to evolve just small variations of those central patterns over time. All the stuff people expect to use around react, on the other hand. That sees huge amounts of churn.
- eitland 5y ago
  Luckily, if you can get everyone to accept it you can often manage just fine without. I'm lucky to be on a team that agreed that redux etc wasn't necessary somewhere before I arrived, and coming from other places that insisted on latest fads it has been blissful.
girvo 5y ago
React itself is incredibly stable, for sure, but its third party dependencies (core libraries most use) are a little less so
- eitland 5y ago
  For what it is worth this is one thing the team I work on did before I arrived there and that I now tell new team members: we actively avoid dependencies, especially redux. React actually works fantastic without if you do it correctly and we rarley have any hard debugging problems that get my head to feel it will explode. I had one big debugging job during the last few months and that quickly turned out to be on the backend.

3np 5y ago

Yeah, I'm talking about having used React extensively since its inception 8 years ago with a couple of 1-3 years periods of being out of that ecosystem and coming back again. I'm sure it's a completely different game these days. Especially I recall that with lifecycle methods, previously idiomatic patterns would be deprecated with stern runtime warning within a year. Like this: https://reactjs.org/blog/2018/03/27/update-on-async-rendering.html https://reactjs.org/blog/2018/03/27/update-on-async-renderin... Granted React team has been way more effective at communicating than the .NET team, again facilitated by a much smaller scope. As for the ecosystem: Anyone else remembers when react-saga was The One Way To Manage Effects? Or going through all the major versions of react-router?

kqr 5y ago

I agree, React itself can be remarkably stable because they found the right abstractions early on and have been able to evolve just small variations of those central patterns over time. All the stuff people expect to use around react, on the other hand. That sees huge amounts of churn.

eitland 5y ago
Luckily, if you can get everyone to accept it you can often manage just fine without. I'm lucky to be on a team that agreed that redux etc wasn't necessary somewhere before I arrived, and coming from other places that insisted on latest fads it has been blissful.

girvo 5y ago

React itself is incredibly stable, for sure, but its third party dependencies (core libraries most use) are a little less so

eitland 5y ago
For what it is worth this is one thing the team I work on did before I arrived there and that I now tell new team members: we actively avoid dependencies, especially redux. React actually works fantastic without if you do it correctly and we rarley have any hard debugging problems that get my head to feel it will explode. I had one big debugging job during the last few months and that quickly turned out to be on the backend.