By all accounts, TypeScript has been a big success for Microsoft. I've seen loads of people sparkle with joy from dousing JavaScript with explicit types that can be checked by a compiler. But I've never been a fan. Not after giving it five minutes, not after giving it five years. So it's with great pleasure that I can announce we're dr...

By all accounts, TypeScript has been a big success for Microsoft. I’ve seen loads of people sparkle with joy from dousing JavaScript with explicit types that can be checked by a compiler. But I’ve never been a fan. Not after giving it five minutes, not after giving it five years. So it’s with great pleasure that I can announce we’re dropping TypeScript from the next big release of Turbo 8.

  • ShustOne
    6•10 months ago

    I think the best take on this is from Rich Harris at Svelte. They are dropping it for internal Dev because they get the same feature set from JSDoc and have no build step, but they keep it for Svelte users who want TS.

    • @asdfasdfasdf@lemmy.world
      1•10 months ago

      I’d think it would make code reviews pretty damn hard to understand without pulling the branch and loading it in your editor. One of the benefits of statically types languages is you see the important bits in the diff at the location they’re used.

      • ShustOne
        1•10 months ago

        True but ideally a PR should be loaded on your machine for proper review. Otherwise you are just blindly trusting the written types anyway and don’t know if it’s correct.