Most of the weirdness comes from being designed for the web, and specifically for working with forms. The value of a form field will always be a string, which is a simple and straightforward idea, but then the trouble showed up when we tried to make it more convenient to work that way.

[–] cmdrkeen@programming.dev 0 points 10 months ago (1 children)

Actually, most of the weirdness comes from having been originally designed in a matter of 10 days by a single engineer working to accommodate a tight release schedule.

[–] Turun@feddit.de 0 points 10 months ago

It's a nice story, but it doesn't make any sense.

The goal of JS - just like with HTML Renderers - is to be as resilient as possible so that even a broken website will still run. You can omit the head tags, and not close your body and HTML tags - the browser will still do its best to render the website. The same goes for JavaScript. You are comparing 1234 to "1234"? I could fail with a catastrophic error and make the whole website crash - or I'll just pretend that you meant to parse the string as a number before the comparison.