• alokir@lemmy.world
    link
    fedilink
    arrow-up
    18
    arrow-down
    1
    ·
    1 year ago

    Typescript is a language, Node is a platform and framework. You can use Typescript in your Node project, they’re not mutually exclusive.

    The way I see it Typescript is more popular than ever, almost all (popular) libraries come with types and every job offer I get they use Typescript.

    And with good reason, our team recently took over a small Javascript app and there are tons of bugs that would never have existed if they were using Typescript. Things like they refactored something but missed to update a reference, or misspelled a variable name, failed to provide a required parameter to a funcrion, referenced a field that existed in another config object etc.

      • I’m not sure this proposal can replace Typescript. It doesn’t support any of the more powerful Typescript features as far as I can tell. Basic types in Javascript are a great step forward, but I don’t expect them to be very popular if they can’t describe things like partial JSON objects for working with APIs.

        Out of all the transpiler steps in “modern” JS, I don’t think I’ve ever seen Typescript suck up all that much performance. Splitting code into streaming files, doing whatever dark magic makes modern JS compatible with IE 9 for some reason, and setting up hot reloads used to be the heaviest part of my workflow. Working with Typescript sucked up a lot of RAM in my IDE, but that as mostly because the types I was working with were created in Javascript that read like code golfing sometimes, generating three or four types for every possible API call.