5 ms·

And this is why there's so much interest in transpiling to Javascript. Rather than commit any time to understanding these often poorly designed semantics, auto

• Hammershaft 2y ago
  It's a tragedy when you think about how many millions (billions?) of man hours have been wasted on javascript because it's the only native scripting language of the browser. Even more tragic is that the original plan was to make scheme the language of the browser.
  • nanomonkey 2y ago
    Well, now you can compile scheme to run on the browser with Hoot (Guile scheme to WASM): https://spritely.institute/hoot/ https://spritely.institute/hoot/
    • shawn_w 2y ago
      There's an experimental Racket to JavaScript compiler too: https://docs.racket-lang.org/racketscript/index.html https://docs.racket-lang.org/racketscript/index.html Ooo, there's more: https://github.com/jashkenas/coffeescript/wiki/List-of-languages-that-compile-to-JS#scheme-like https://github.com/jashkenas/coffeescript/wiki/List-of-langu...
• MatthiasPortzel 2y ago
  JavaScript is very well designed for backwards compatibility. Many of these examples are showing off old features that were intentionally changed in order to make more sense next to the new features that replaced them. But presenting both next to each other and highlighting a difference in behavior makes the language look inconsistent.