I have had lots of these conversations with other people who think they are good at what they do.
This line of thinking kills companies, because the prototyper they hired for their "MVP" doesn't like frameworks. A year later he/she is gone and I'm rebuilding their app as an angular app.
You don't have to agree with me, but I am right. Millions of of dollars in contracts and a resume full of happy returning clients says so.
If people choose not to listen to what I have to say it has no impact on me at all. I will continue making a living off their mistakes.
You mean the people you refereed to as lacking technical expertise that you profit from? "Happy client" does not equal "superior code". Often clients will be happy just seeing the page load.
You implied earlier that a be-spoke js app by definition is spaghetti, poorly documented and generally inferior. I can't subscribe to that idea. I've seen the reverse as true also.
Risk of failure is what everyone wants to avoid. Another risk to avoid... Mediocrity. MVP is mediocre by definition, and the quickest way there is to slap a few frameworks on top of each other. Bells and whistles yet more.
I suppose striking the balance is what matters, and "right tool" and all that. But the right tool could indeed be a be-spoke app.
They tell me that you can cover the tracks of your desasters long enough to move on, so that problems surfacing later are attributed to the maintenance programmers and not you, even if your "great" choice of frameworks were the real reason.