3 ms·

If you want to know what the future of Javascript looks like, look at the present of Java. It's a monster language with maximum bureaucracy, but it's not going

If you want to know what the future of Javascript looks like, look at the present of Java. It's a monster language with maximum bureaucracy, but it's not going anywhere, since most large companies already have legacy systems built with Java. But I also am not a fan of this direction just like you. My personal thought is, JS will never lose its dominance just like Java, and it will grow and grow until it becomes a monster like the Java ecosystem, and it will become shittier and shittier. But that is only until something disruptive comes along that will decimate the influence of the desktop web browsing experience as we know it.

niftich 10y ago
It's worth noting that WASM will (eventually) enable other languages to run in the 'browser VM' and this loss of JS' monopoly (whether as a source language or a compilation target) will cause some of the pace of innovation to shift away from JS and onto WASM. Right now, the ecosystem has a lot of churn for exactly three reasons: - browser vendors keep adding 'web platform' APIs that are only callable through JS - new spins on paradigms are popping up on how to structure single-page applications - the JS language itself is getting new features after being stagnant for years When any one of these quiets down, the churn will slow.