I’m definitely not interested in going back to C or C++! But look closer at WebAssembly. It allows other people (the people building frameworks) to create platforms we can use in our high-level languages.

For example, if you use Blazor you’ll be programming in C#, complete with managed services like a garbage collector, and using high-level APIs that mimic the .NET Framework. The performance of WebAssembly is only important in that it allows this environment to work as well as JavaScript already does.

Another way to look at it is WebAssembly today is about a narrow range of performance optimizations that are important for emulators, games, etc. WebAssembly tomorrow could be about bringing new languages and frameworks that will compete with Angular/React/Vue.