Microsoft had a Visual Basic variant (VBScript) in IE that got some attention back in the 90s; it's probably just as well that JS won instead of that...

In modern webdev type="module" is used to indicate an ES6 module and type="importmap" to include a JSON table of paths to modules. Still basically JS, but the parameter is still used in a meaningful way.

It still suffers from not having access to the DOM and other APIs the browser supplies. That's being worked on, I believe.

Without that, you still need a JavaScript layer in-between at the very least. At that point, you're not gaining much from running in WASM.

Doesn't a browser need to have javascript enabled to even run WASM? That beats the entire point of getting rid of js

But that was something that had to be installed on the system and integrated into the browser, not quite what i'm asking as it wasn't an alternative browser per se

I see that as mostly positive 😆

Your browser wouldn't be able to load any js based sites

You could make a browser capable of loading both, and I think it already happened. The problem is, that a browser supporting more languages than necessary, was never successful enough to get mass adoption and on the internet you need mass adoption to survive.

I'm aware and not really worried about that

Says Gooegl

Not quite what I'm asking, that's just python under a js wrapper - block javascript and none of that works.

Interesting. Too bad it only supports HTML4. The ELinks fork doesn't mention whether it supports HTML5 (canvas and other more recent stuff), so I suppose it doesn't

And now it's just chrome like almost all other web browsers

Typescript doesn't run on the browser. But I'm pretty sure we will see native typescript soon. At this point, TS is practically the industry standard for developing serious JavaScript.