I was talking to my manager the other day, discussing the languages we are using at $dayjob. He kind of offhandedly said that he thinks TypeScript is a temporary fad and soon everything will go back to using JavaScript. He doesn’t like that it’s made by Microsoft either.

I’m not a frontend developer so I don’t really know, but my general impression is that everything is moving more and more towards TypeScript, not away from it. But maybe I’m wrong?

Does anyone who actually works with TypeScript have any impression about this?

  • aidan@lemmy.world
    11·
    7 months ago

    We use TS on the back end to leverage our teams existing skill set and libraries we’ve built up.

    I know you said this, but I’m still curious why not just something like Go, which I was able to basically learn in 3 days- just coming from a mostly JS and C++ background

    • sloppy_diffuserEnglish
      2·
      7 months ago

      I’m coming from a Haskell/Scala background. This job just pays more. TS has been “good enough” for types. I don’t think I could be as effective without them at this point.

    • gibson@sopuli.xyz
      2·
      7 months ago

      As a Go dev, its simplicity is arguably taken too far. For example there are no union types or proper enums

      • JulianRR@lemmy.world
        3·
        7 months ago

        Yeah. I started as a C++ dev, fell in love with Go, then ended up on Rust.

        Felt like a nice middle ground of “It’s got the types I need, but it feels good to dev on”

        I really did enjoy using go for smaller projects though, would do so again.

      • aidan@lemmy.world
        1·
        7 months ago

        That’s fair, I know they’re actively rejecting inheritance, but I wish you could make like a prototype. Like say, a function can take a struct with these fields. Which yeah an interface can do but is much more clunky