中文 (Chinese Simplified)
That assumes there's boilerplate in a model, a controller or a view. Why is there boiler plate there? There shouldn't be. Writing a modern MVC app is simple. Writing an Angular app actually forces you to write Angular code, not MVC code. Same with React. Etc.
MVC doesn't require a framework or a library, it's a concept. It just requires models, views and controllers. And it's also pretty much not needed at all in the front end unless you're doing logic solely in the front end (which not many sites do at all). It's usually used to grab data via JSON.
Frameworks don’t tend to abstract complexity away, libraries do. More often than not the framework is built on a library and that library isn’t necessarily the one in use by the developer and it leads to bloated code messes.
This doesn’t matter if design patterns are taken into account and code is modular
It used to be the case that network speed was an issue and loading partial pages was much quicker than loading whole pages. This is generally no longer the case