11–20 of 207 posts
The post mentions one of the most important factors in TypeScript’s adoption: it launched, from the start, with good tooling.
Earlier quoted context omitted.
That unfortunately hasn’t helped C# become more popular outside of Microsoft legacy shops even when it did go cross platform and open source.
What is a "Microsoft legacy shop" ?
Wanted to try it, proceeded to install it with npm and it was incredibly scary, both the amount of stuff it pulled in and various warnings. No thanks, I'll stay with languages with more self-contained compiler.
But yeah, the tooling is kind of bad and it is all written in OCaml, while TypeScript is in TypeScript…
>TypeScript never set out to build a separate, distinct, and prescriptive language. Instead, TypeScript had to be descriptive. Sadly, the majority of people writing Typescript rarely care about descriptive and readable code these days. Somehow the focus shifted from using types to better understand complex systems through the code itself , to writing whatever polymorphic union type abomination that yields the best In…
TypeScript is great, but it is also still very far from being complete in my opinion.
I used to do mostly Java and a bit of TypeScript, changed teams and now do mostly TypeScript and a bit of Java, and this unfinished feeling is striking, even for relatively basic things (enums).
I think the modern compiler options / TypeScript rules such as "hey this variable can be undefined but you didn't specify it", "hey, it can also be null, don't forget that" are commandable, but just don't work well for the web. I know it's configurable, but it just makes for a bad experience.
Still, love TypeScript. I wouldn't do any JavaScript project anymore, installing the TS compiler is always my first step.