• PenguinCoder@beehaw.org
    link
    fedilink
    English
    arrow-up
    13
    ·
    edit-2
    1 year ago

    Because at the end of the day TypeScript is still Javascript and it’s still bad. Just has some verbose formats to try and make weakly typed language (javascript) appear to be strongly typed. It adds more build steps to what shouldn’t be there; build steps make sense for apps, they make much less sense for libraries.

    https://dev.to/bettercodingacademy/typescript-is-a-waste-of-time-change-my-mind-pi8
    https://medium.com/@tsecretdeveloper/typescript-is-wrong-for-you-875a09e10176

    • pjhenry1216@kbin.social
      link
      fedilink
      arrow-up
      8
      ·
      1 year ago

      I’m sorry. Whoever wrote that should give up trying to write articles. It’s poorly written and will never convince anyone to change their mind. It’s shit. “I know how to convince people they’re wrong. Insult them. Setup a ton of strawman arguments. Genius.”

      Whoever wrote that is bad and should feel bad.

        • pjhenry1216@kbin.social
          link
          fedilink
          arrow-up
          5
          ·
          1 year ago

          Second one. Just realized there were two. Being close together and the first being long enough to get trailing “…” it all just looked like one big link when I first saw it. May just be Kbin displaying it that way.

    • Fushuan [he/him]@lemm.ee
      link
      fedilink
      English
      arrow-up
      3
      ·
      1 year ago

      build steps make sense for apps, they make much less sense for libraries.

      This might be true, but it’s not about build steps, it’s about having detailed iformation of the types of the objects that the library is serving. not knowing the typing of the functions a library is serving is… poor. Maybe typescript is too strict and having something like type hinting like python has would be enough since linters pick up the hints from the libraries, but doing just JS only fuck the people that use the library.