"we should be doing things correctly from the start"
2 years later:
"the maintenance of custom doesn't deliver business value and makes recruitment and on-boarding increasingly difficult. We should rewrite in $framework since it's well known, maintained and flexible enough to do whatever they need"
...
There are lots of anti-patterns around this ;)
I've seen too many teams fight Rails (in particular) to implement new product features to agree with this. The framework never grows, it stays the same size and eventually becomes a straitjacket for the product.
Like I said, though, this isn't a reason to not use a framework at the start. As long as everyone realises that at some point it'll need to be rewritten.
assuming that the more the framework does also means the less the framework allows you to do yourself. which is a pretty reasonable assumption of course.
You give people a more powerful product and they’ll use the power.
This is a great example of "fighting the framework". React + SVG got them from nothing to a working product. But then they had to rewrite completely to solve problems in the product because the framework no longer fit the product. I've seen this so many times.
But it's hard for people to believe when they start out and choose the "perfect" framework for their product:
"you will eventually have to rewrite your entire product because that's easier than fighting the framework to make it do what you need"
"no, we won't, this $framework is flexible enough to do whatever we need"
"OK, good luck"
2 years later:
"we're rewriting the product completely because $framework wouldn't let us do $thing"
Not that I'm advocating for not using frameworks, just for people to realise that eventually (almost) everyone fights the framework and rewrites. And the more the framework does, the earlier the fight begins.