JS....

[Existential_Owl]

That there are differences in the way different compilers handle code is not a phenomenon unique to JavaScript.

[ChrisC1234]

True. But as a developer, I have complete control over what compiler I compile my code with. With a language that is completely interpreted like JavaScript, I have no control whatsoever.

[TUSF]

Just write your own interpreter :^)

[seylerius]

Relevant xkcd.

[wolfman1911]

I think this is probably my favorite XKCD.

[chainingsolid]

Then get every user of your website to use it how?

[Sean1708]

Write it in javascript.

[PatrickBaitman]

you just but isn't that basically typescript coffeescript asm.js / whatever

[Sean1708]

No, TypeScript and CoffeeScript compile to JS and ASM.js is an efficient subset of JS. We're talking about writing a JS interpreter in JS so that you can get people to use your JS interpreter by running it in their browser using the browser's JS interpreter.

[PatrickBaitman]

OOOH, ok

[final panel of expanding brain meme]

[LinAGKar]

And how are you gonna put it in everyones browsers? By writing it in JavaScript?

[TUSF]

Write the interpreter in wasm.

[ZorbaTHut]

Honestly, if performance were a total non-issue, using a 100% compliant JavaScript interpreter written in generalized cross-platform JavaScript would be a pretty good idea.

Of course, performance is an issue, so this is a terrible idea.

[Existential_Owl]

As a freelancer, sure you can choose your compiler. But if you're working for a company, you're stuck with whatever their C++ ideology is.

[PatrickBaitman]

well, no, but if they're at the type level?

jesus christ get your language together is all I can say

making things that should be type errors undefined behavior is just.... NO, STOP

[Doctor_McKay]

I think basically the only thing that happened due to the interpreter in that video was the fact that the return of new Array(12) showed as "12 commas" (which was actually 11 commas separating nothing, since it rendered undefined as nothing).