this post was submitted on 08 Aug 2023
1267 points (90.0% liked)

Technology

59415 readers
1166 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots


founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[โ€“] Freesoftwareenjoyer@lemmy.world 0 points 1 year ago (1 children)

Most of the examples listed there are issues that don't affect real applications. It's just garbage code, so the output ends up being garbage too. Programmers don't write code like that, unless they are doing it as a joke. A few of those examples can be real issues sometimes, but they are not that big of a deal to an experienced JavaScript programmer.

It's an imperfect language like any other.

[โ€“] grue@lemmy.world 0 points 1 year ago* (last edited 1 year ago)

but they are not that big of a deal to an experienced JavaScript programmer.

A well-designed language wouldn't require "experience" for stupid gotchas like these to not be that big of a deal in the first place.

After all, I'm sure a sufficiently "experienced programmer" could adapt to anything up to and including fucking Malbolge if necessary, but that doesn't mean it's equal to a language that's actually good.

Differences in quality between languages are real, and Javascript is closer to the bad end of that spectrum.