> You're so concerned with development speed, yet you're rewriting the same thing in a new framework every 2 years.
I think that meme gets thrown around a lot, and it used to be true, but the framework churn of JS has largely stopped at this point. A lot of us (me included) have been just using the same stack for several years now.
Sure, React has evolved since 2015/2016 (e.g. the move to function components and hooks) but the old code still runs, with minimal to no changes. Patterns and best practices have largely been established. You can entirely avoid the bleeding edge stuff and still be productive.
Elsewhere in this thread there are comments about needing to continue pace to move beyond React. I don't think we've seen the end of the churn. I agree that React is a pretty stable base these days and you can just work with that, but it's gotten long in the tooth in places so new frameworks are still sprouting up.
Old code continuing to run isn't what people mean by churn though. jquery still runs. The underlying browser APIs are stable. But you can't say React has stable patterns and best practices when the classes->hooks thing has happened so recently.
I think that meme gets thrown around a lot, and it used to be true, but the framework churn of JS has largely stopped at this point. A lot of us (me included) have been just using the same stack for several years now.
Sure, React has evolved since 2015/2016 (e.g. the move to function components and hooks) but the old code still runs, with minimal to no changes. Patterns and best practices have largely been established. You can entirely avoid the bleeding edge stuff and still be productive.