@kytta For me, It’s all of the answers at the same time, so I hit “akshually”

@kytta

ts is an example of "embrace, extend, extinguish" for a generation of developers who do not remember "the halloween papers" and have drunk the "microsoft loves open source" kool-aid hook, line, and sinker

it's an example of how one of the most toxic vendors interposes themselves as a gatekeeper, under the guise of an open source license, in response to a legitimate need for a better js

It's JS with sensible inheritance but way too much this

@kytta, TypeScript is a very elaborate linter for JavaScript. Despite its appearances, it's not adding anything of substance, only a large exoskeleton that gives more power in some cases but is a drag in others.

@kytta from a language theory perspective, TS is a superset of JS, so its Venn diagram would be a larger circle around JS.
So all JS is TS but TS comes with extra type annotations, interfaces, etc. which act like a foundation for much better intellisense and overall tooling.
At runtime of course TS is transpiled down to JS so there's *little* difference between the 2.
For me, TS is a useless headache, but I see how it can make code a bit easier to reason about in large teams and projects. Meh :)

@kytta My understanding might be incorrect but as I understand it a well-typed TS program can *almost* be directly syntactically lowered to an equivalent JS program. "Almost" because I believe there's some extra sugar for some ergonomics things that do leverage the type information, but I don't know the specifics since I don't do TS progamming actively.