jsfuck VS brainfuck.go

Also worthwhile is their home page: https://jsfuck.com/

That wasn't the point of this exercise - nobody is saying that these are actual code is examples you'd see in real life.

The point is that in lots of languages these statements would simply result in compile time errors. In JS, though, the type coercion rules are so loose (and in many cases extremely non-obvious) that you can see this head scratching behavior.

It's the same underlying behavior that leads to very cool/very insane stuff like JSFuck: https://jsfuck.com/

That's partly why, among other ridiculousness involving type, it's possible to code with only []()!+ in JS.

You forgot about JSFuck

If you want to see why JavaScript is such a ~shitty~ interning language, look at this: https://jsfuck.com/

jsfuck.com

First of all, consider security. As with any REPL, malicious actors could try to send their victims code to execute locally on their machine to whatever effect, so at least a warning is in order. Validation against such attacks is utterly useless, just take a look at JSF*ck and give up.

BF! Check out the compiler I wrote https://github.com/ronnathaniel/brainfuck.go