The counterpoint is that if you don’t adopt a framework you end up with a “framework” you built yourselves that people outside your team don’t understand, is generally poorly documented and needs constant work to add features existing frameworks already have. There are common features needed on the FE and common problems to solve, why not at least start with something instead of nothing?
Yes this is a problem I've seen. It's impossible to find people who can be immediately productive because they've never seen your internal framework before. Even if it's extensively documented, it still takes time to learn and internalize. For long-term hires, it's not the worst, but if you ever temporarily need extra devs, you're SOL.
I am not sure this is true . As I wrote elsewhere, almost everyone wants a web app or thinks that they have a web app, but usually it is just a dynamic website. You do not need to build up a framework to have a dynamic website.
