I also did what the parent did. I'm using mine on several enterprise projects. And I'd also argue that devs spend //more// time implementing updates due to fram

I also did what the parent did. I'm using mine on several enterprise projects. And I'd also argue that devs spend //more// time implementing updates due to framework churn than for maintaining their own framework. After mine was "done", it was done. There is no code churn, all the features are in, tight code, etc,...so now I only spend time creating/expanding my products. The discussion today about React v6 is exactly what we get to dismiss (as well as any along the way from v2 - v5) since our framework work is done. Granted, you're absolutely correct when you say new devs have to learn all the proprietary ways of your framework. But even then, since the framework is such a small percent of the overall knowledge dump for a new hire, I'd argue, that it's not much of a concern. It'll take months to learn the systems, and maybe a week(?) to learn the framework. And to be fully honest, I haven't learned React/Angular/Vue (did learn KnockoutJS back in the day), and if I need to hunt for a job, then yes I'm behind the curve.