• killeronthecorner@lemmy.world
    link
    fedilink
    arrow-up
    4
    ·
    1 year ago

    You’re describing many things that are not JavaScript the language. If you create and use tools that will stop you then yes they will stop you.

    • newIdentity@sh.itjust.works
      link
      fedilink
      arrow-up
      1
      ·
      edit-2
      1 year ago

      I said ESLint. Not Javascript. ESLint is a linter for JavaScript. That’s why I put JavaScript in brackets. Some people don’t know what ESLint is. I’m talking about ESLint the whole time. Its not JavaScript specific but it’s mostly used for JavaScript

      You yourself are talking about ESLint. You said that ESLint won’t prevent me from creating unused variables and functions when it clearly does. It won’t even run and throw an error

      Edit: ohh it’s a Lemmy bug. The comment didn’t update yet. Originally I said “ES6” then I changed it to “JavaScript” and then I changed it to “ESLint (JavaScript)”

      • iByteABit [he/him]@lemm.ee
        link
        fedilink
        arrow-up
        4
        ·
        1 year ago

        There’s a load of confusion in this thread.

        What the post is about is compiler based clean code enforcement. JS doesn’t do this, but your editor in combination with ESLint prevents you from running the program. However this isn’t a general JS thing, just the way your setup works.

      • killeronthecorner@lemmy.world
        link
        fedilink
        arrow-up
        3
        ·
        1 year ago

        Just saw your edit, and yeah, that makes sense as to the confusion.

        Either way, your comment enquired as to whether it was “the same” and it still isn’t because for Go it’s a language feature and ESLint is not a language, it just allows you to create similar behaviour for JavaSvript which, by default, does not exhibit that behaviour.