Why Typescript is bad
1.81K subscribers
72 photos
70 links
All topics related to TS

chat: @why_typescript_is_bad_chat
contact: @stuneak
Download Telegram
Extension persistently shows a type of expression on top of // ?^ mark. It's indispensable for debugging of deeply nested type computations.

https://marketplace.visualstudio.com/items?itemName=Orta.vscode-twoslash-queries

10x @dkzlv @khraks_mamtsov
Variance annotations are unsound. Contravariant type variable can be pronounced to be covariant, and TS couldn't care less.

Code. Issue.

Also here is an example that actually crashes in runtime.
Forwarded from TypeScript Stories
3️⃣2️⃣
Wrong type inference with Capitalize and Uncapitalize utility types.

▶️ Playground
JSON.stringify can return undefined and it is ok??

Playground.
Eh?
That's it.
TypeScript decided to commit sudoku by rewriting its compiler in an even worse language: Go.

The only reason given is "performance". De facto it means the language is so bad they can't use it for its own compiler anymore.

https://devblogs.microsoft.com/typescript/typescript-native-port/
Playground

@js_monk Thanks for sharing this madness!