The only way your comparison works is if your point is "Framework driven apps are never good". I've lost count of the number of times I've pointed out that a good vanilla JS is always going to be better than a bad framework driven app. One is a good app and the other is a bad app. It's obvious, and therefore not a useful comparison.
The valid, useful test is whether or not a good vanilla JS app can be better than a good framework driven app.
> The valid, useful test is whether or not a good vanilla JS app can be better than a good framework driven app.
A much more useful test is to look at the average vanilla and framework app. Obviously the best framework app or vanilla app is gunna be pretty good regardless.
Do frameworks encourage bad/lazy coding? Do they make it very easy to half baked something but very hard to create something polished? Does the constant churn of frameworks mean that a project can never be mature and stable?
Is plain JS too restrictive? Do you have to reimplement react yourself if you want to make a good website?
The valid, useful test is whether or not a good vanilla JS app can be better than a good framework driven app.