I've read different defenses for JavaScript for cases like this, which usually runs somewhere from you shouldn't be doing that anyway all the way up to if you just understood the language better you'd know why. While I agree with both of those points strongly as general principles, JavaScript also violates the principle of least surprise enough to make it concerning.

For what it's worth, I do like JavaScript. I really don't think that there is any perfect programming language.

[–] 5C5C5C@programming.dev 15 points 4 months ago (3 children)

I really don't think that there is any perfect programming language.

You'd be wrong 🦀🦀🦀🦀🦀

[–] 9point6@lemmy.world 11 points 4 months ago (1 children)

That's a weird emoji to use for elixir

[–] sparkle@lemm.ee 3 points 4 months ago

Elixir? Is that the weird older cousin of Gleam?

[–] skulbuny@sh.itjust.works 3 points 4 months ago

Compile times say otherwise

[–] bahbah23@lemmy.world 2 points 4 months ago

Fair, I haven't used Rust so I don't really have an opinion on it.

[–] palordrolap@kbin.run 8 points 4 months ago (1 children)

JavaScript, like some other languages of the time, was designed with the Robustness Principle in mind. Arguably the wrong end of the Robustness Principle, but still.

That is, it was designed to accept anything that wasn't a syntax error (if not a few other things besides) and not generate run-time errors unless absolutely necessary. The thinking was that the last thing the user of something written in JavaScript wants is for their browser to crash or lock up because something divided by zero or couldn't find an object property.

Also it was originally written in about five minutes by one guy who hadn't had enough sleep. (I may have misremembered this part, but I get the feeling I'm not too far off.)

[–] zarkanian@sh.itjust.works 5 points 4 months ago

It was 10 days, but, yeah, not a lot of time, especially for one guy. (That one guy was Brendan Eich, by the way.)