As someone who's written custom mvc's in vanilla js/ts on an as-needed basis since long before vue or react were a thing, I agree completely. The reason I've ne

As someone who's written custom mvc's in vanilla js/ts on an as-needed basis since long before vue or react were a thing, I agree completely. The reason I've never tried to formalize my frameworks into something for the community is that I don't need another full time job, and don't have any desire to hear the moaning and abuse that inevitably comes when you open source a tool you think will speed up development. I.e. everyone has an opinion. I don't use frameworks because I don't like my codebase sliding out from under me, when I have projects in production for over 10 years that just need occasional new features. The froth of frameworks and keeping up with them seems to be maximally important to devs looking for office jobs... once you freelance and have time to roll your own, it's just kinda the same routine over and over. I feel bad for folks who have to spend such an inordinate amount of time just learning and working around new tooling. In the end if you spend the time writing it yourself you end up with a better understanding of its strengths and weaknesses. You never need to consult Stack overflow to find out how to deal with your own MVC stack.