• MrGG@lemmy.ca
      link
      fedilink
      arrow-up
      2
      ·
      1 year ago

      That is disturbing. From my perspective, anyway. There are already so many great (and more appropriate) stacks for web backends, why Frankenstein a Frankenstein into it?

      • Knusper@feddit.de
        link
        fedilink
        arrow-up
        10
        ·
        1 year ago

        Well, usually because you’ve got a team of frontend folks needing to do a backend.

        There’s one other advantage, which is that you can have a compile-time shared model between backend and frontend. You also have that advantage with WASM, but not with a traditional backend/frontend technology split…

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

          Compile time is my biggest issue with TypeScript. I’ve used JavaScript for decades with compile time measured in, what, a millisecond or two. Having to wait for TypeScript drives me nuts.

      • The Cuuuuube@beehaw.org
        link
        fedilink
        English
        arrow-up
        3
        ·
        1 year ago

        🤷 people like nodejs and people like type hinting and IDE reflection. Typescript helps a lot with that