• atheken@programming.dev
    link
    fedilink
    English
    arrow-up
    14
    ·
    edit-2
    1 year ago

    Yeah, dropping typescript and then codifying type information in jsdoc is comical.

    The only thing I would say about your experience is that “dropping TS for go” is a little bit misleading, and it doesn’t really sound like it bears on the general debate of “TS vs. JS” - go and other static languages generally fit a different niche in my opinion, and can be a better option for certain kinds of systems.

    If you’re building anything of even moderate complexity, or with more than one person, you really need the types and modularity that TS provides.

    I guess it’s also worth noting that JS has actually been influenced/adopted some key features from TS over the years, so it’s possible to do a few things with it to make stuff that’s a bit more maintainable.

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

      Yah, 100% agree. So in my case, Typescript is actually a better fit niche-wise… but I finally reached the point where I didn’t want to cope anymore with flawed things it was inheriting from Javascript, so it was especially ironic to me when I saw this and thought maybe I’m not the only one, only to discover that the message was “SIIIKE we love the flawed things! It’s the improvements we’re getting rid of.”

      I mean every project is different and they’ve got a right to do what they want. It was just a hilarious surprise for me.