• ☆ Yσɠƚԋσʂ ☆OP
    link
    fedilink
    arrow-up
    6
    ·
    3 years ago

    It’s really not a great situation with package management in Js land, and having two predatory companies own major tools and package repositories certainly doesn’t help things.

    • AgreeableLandscapeM
      link
      fedilink
      arrow-up
      4
      ·
      3 years ago

      All the more reason to not use JS. Being a terrible language is one thing, having a terrible ecosystem is worse.

      • ☆ Yσɠƚԋσʂ ☆OP
        link
        fedilink
        arrow-up
        5
        ·
        3 years ago

        Definitely, it’s sadly hard to avoid entirely with it being the main driver for the web. Stuff like ClojureScript is nice since it’s pretty much its own ecosystem and you can opt into Js stuff if you really need to.

        • AgreeableLandscapeM
          link
          fedilink
          arrow-up
          5
          ·
          edit-2
          3 years ago

          Kotlin can also compile into JS and is more familiar to most JS developers. More options are good as a general rule and we’re starting to see more players in this space.

          You know it’s bad when you’re using a lower level bytecode or native language to compile to a high level interpreted language just to avoid said high level language.

          • ☆ Yσɠƚԋσʂ ☆OP
            link
            fedilink
            arrow-up
            4
            ·
            3 years ago

            Yeah, it’s kind of an amusing situation. I literally just treat Js as bytecode nowadays. I haven’t had to write a line of it in years.

            • AgreeableLandscapeM
              link
              fedilink
              arrow-up
              4
              ·
              3 years ago

              Honestly, production JS is so obfuscated and processed and hard to read as an outsider that it’s essentially bytecode. Reverse engineering JS in a webpage is a common security CTF challenge.