After reading the entire thread I am still in the dark about what exactly the author wants to see changed.
The narrative that frameworks = bad and vanilla js = good falls apart quickly IMHO in medium to large sized projects since the complexity has to be abstracted in some way in order to reach a realistic timeframe for completion.
I think in some ways this is also a question of specialized vs universal tools. If I plan a vacation with friends I believe I could do it 90% of the way just as well with a plain old shared word document/todo list.
As a nearly daily user of Google Stadia I have to disagree. I use Stadia in two different households, one with a 50 Mbps connection (where Stadia works perfectly) an one with a connection capped at 10 Mbps down and 1 Mbps up. The 10 Mbps connection only allows for 720p gameplay and I get frequent stuttering every 5 minutes or so but this doesn't really ruin the experience with most story driven games like Red Dead Redemption 2 or AC Odyssey.
At first I was surprised by the playability of Stadia at such a slow connection myself but even though I cannot play shooter games I wouldn't go as far to call the experience I get with the 10 Mbps connection 'unplayable'.
The narrative that frameworks = bad and vanilla js = good falls apart quickly IMHO in medium to large sized projects since the complexity has to be abstracted in some way in order to reach a realistic timeframe for completion.