JavaScript might become two languages (and it's dramatic)

split up into Java and Script

I like the idea, but for it to work the runtime needs to be simple, like .NET runtime. C# keeps getting new features every year, but most of the time they don't cause any change to the runtime. The high level C# code gets lowered (ex.: pattern matching is lowered to a bunch of if-else statements) and then finally compiled to .NET intermediate language. This strategy works because the language can get new features that usually don't require any change to the runtime, keeping it simple. To be honest, that's what I expected WebAssembly would be when it was first announced.

After "A new JavaScript framework every day" and "A new runtime every day", let JavaScript introduce you to an even better concept : "A new JavaScript language every day" !

It's not the first time JavaScript has seen a split The first one was during ECMAScript 4's development, due to which we got both ECMAScript 5 and ActionScript

babe wake up, two new javascript based javascript abstractions just dropped

19:28 the JS ecosystem has been evolving at an insane pace literally since I started professionally. It's been the case for at least that long that you will learn one tool, and in three months it's obsolete and you need to learn another. Sometimes the new tool is a way to not need to learn the next tool by combining all the tools in one, then that also becomes obsolete. JS devs are, by and large, a group of insane people who need to lay off the fucking methamphetamines for eight minutes. This is not the browsers' nor the users' problem.

How this sounds for me: - The JS ecosystem is an absurd clusterfuck. - There is a proposal to do X, which should help slow down the enfuckening of things. - But if X happens it will accelerate the enfuckening of other things.

Seems to me that if you need all these features the focus should be on making WASM capable of controlling the DOM so other languages can compile into something usable on the web. If JavaScript can’t be everyone’s ideal language for the web then it should only be the default and WASM can open the door to other options. But also if implementers cant implement either the build or browser side of things fast enough. Then I think our community goes too fast and doesn’t think enough about the consequences of each change to the standard. We can’t even transition to ESM in a timely fashion so maybe slow down a bit?

A proposal to stay the same

Maybe the community should resolve esm vs commonjs before another fork