[codingdave]

I think you may have lost the forest for the trees. For as broad of a question as this, the different web frameworks you listed are all just that - web frameworks. That is just one area of programming, and the differences between each framework are trivial in a multi-decade view of things.

What is more interesting is your points towards hardware limitations, and that seems like more of an area in which such a question would have meaning. I tend to think less about what we will code, and more about where that code will run, and how low/high level it will be -- Will we still be coding to browsers in 30 years? Will firmware still be a black box for most people, or will your average joe start to play in that realm? Will coding be a specialty, or will it be as pervasive as knowing how to read and write? If everyone on the planet could at least code to a basic level, and all devices had at least a minimal API to configure, what will that even look like? Will Legos have embedded code, so 4 year olds can assemble blocks and do robotics instead of just static toys?

I have no idea on any of those answers... but those are examples of the kinds of questions we should be looking at, not whether React or Angular will have more longevity, because frankly, in 30 years, very little of what we are doing today is going to have any relevance.

[anonymousDan]

One interesting prophecy I read recently is that the emergence and widespread availability of NVRAM (non-volatile RAM) could shift the bottleneck in most web applications from the disk to the CPU. One implication of this is that the relative inefficiency of current high-level web programming languages could see a shift toward more efficient languages (e.g. Rust?).