• arc@lemm.ee
    link
    fedilink
    English
    arrow-up
    14
    arrow-down
    2
    ·
    1 year ago

    JavaScript is a victim of its own popularity. It was originally meant to be scripting glue to do little actions in the browser while the real work was done in Java (LiveConnect) apps. But Java got jettisoned, JavaScript became more important and became the thing we love and hate today.

    • grue@lemmy.world
      link
      fedilink
      English
      arrow-up
      4
      arrow-down
      1
      ·
      1 year ago

      JavaScript is a victim of its own popularity.

      No, that’s not the issue. If Javascript were well-designed we wouldn’t hate it, but it wasn’t.

      • Freesoftwareenjoyer@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        arrow-down
        2
        ·
        1 year ago

        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
          link
          fedilink
          English
          arrow-up
          3
          arrow-down
          1
          ·
          edit-2
          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.