Will JavaScript type annotations kill TypeScript?
The creators of Svelte and Turbo 8 both dropped TS recently saying that "it's not worth it".
Yes: If JavaScript gets type annotations then there's no reason for TypeScript to exist.
No: TypeScript remains the best language for structuring large enterprise applications.
TBD: The existing user base and its corpensource owner means that TypeScript isn’t likely to reach EOL without a putting up a fight.
I hope they both die. I mean, if you really need strong types in the browser then you could leverage WASM and use a real programming language.
I don’t know and I don’t care.
Anant Jhingran
Anant Jhingran

Anant is the founder and CEO of StepZen, a startup with a new approach for simplifying the way developers access the data they need to power digital experiences. With a career that spans IBM Fellow, CTO of IBM’s Information Management Division, CTO of Apigee, and product leader at Google Cloud, Anant has spent his career at the forefront of innovation in databases, machine learning, and APIs. At StepZen, Anant is enjoying creating a company that brings his love of these technologies together to simplify, accelerate and scale frontend development.

STORIES BY Anant Jhingran
There Is a Bright Future for AI-Driven Integration
APIs Are Where Fun Happens
The Case for a Federated Data Access Layer with GraphQL
GraphQL Makes Data Liquid — What It Means for Data Protection
A New Architecture for APIs Part II — Declarative Implementation
A New Architecture for APIs
What GraphQL Can Learn from Databases
GraphQL and Graph Data: Two Sides of the Same Coin?
GraphQL Is Built for Federation, But Don’t Do It Wrong
OpenAPI and GraphQL: The Chunnel Problem
GraphQL APIs: Great for Adoption, But Are They Secure?
The State of Introspection for REST and GraphQL APIs
Why Backend Developers Should Fall in Love with GraphQL too
GraphQL: Bridging the Gap Between Databases and Your Apps
Decoupling Frontends and Backends with GraphQL
Why You Shouldn’t Host Your Own GraphQL Endpoint