Big projects are ditching TypeScript… why?
youtube.com
Why are some big open-source projects like Turbo and Svelte dropping TypeScript in favor of vanilla JavaScript? Learn about the pros and cons of TypeScript#p...
  • alokir@lemmy.world
    1·
    1 year ago

    The title makes it seem like it’s a wide spread thing in the industry but according to the video it’s 3 frameworks.

    Yeah, it’s additional work but I’ve found that really convoluted or complex type definitions usually mean you should consider refactoring. Of course this is a bit different when it comes to developing frameworks where you might want to support a bunch of different use cases.

    Maybe I’m biased because I’ve been using TS ever since it first came out.

  • ComeSweetDeath@programming.dev
    11·
    1 year ago

    good. typescript has always caused us more headache than it worth in all my projects. I bill my clients extra for it if they make me work on it.

  • ChaoticNeutralCzech@feddit.de
    01·
    1 year ago

    Opinion from me, a JS beginner: Vanilla is good enough now. If your IDE lets you type common structures like document.getElementById("") with shortcuts, I find no need to use a framework. Also, vanilla works better in offline projects.