@krtirtho
Nah bro, any JS related tech/library/framework is never untold. It's the most told stories ever. TBH, even my non-tech dad knows what and why Typescript was born
@Kampouse
i love when people get the most important part wrong :( its not remade from first principle "its a port" and that why it was in go because of the similarity of go and js
@elias6406
TypeScript is not a runtime type checker. It only checks types at compile time. Once the code is compiled to JavaScript, all the types are erased. So even though ts helps catch bugs early during development, it doesn’t enforce any types at runtime. If you need runtime validation, you have to add it manually or use libraries like Zod. Still a great tool for dev mode— just worth clarifying that it’s not enforcing types while your app is actually running! It acts similarly to js during runtime
@CarrigansGuitarClub
I actually believe Microsoft's future is in TypeScript not Blazor.....which hasn't caught fire!
@aintnochange
TypeScript is GREAT, but the only thing I don't like about it is how some TS libraries are written. E.g. looking into React's source code, all I can see is a type hell with union types on top of union types on top of union types (and so on). Btw, I think if JSDoc was a bit easier to use (templates especially), typescript's supremacy would not be that impressive.
@azizweslati4639
your way of telling the story is amazing
@BobFrTube
I argue for the term "type annotation" rather than "strict types" -- that fact it's not strict is key. For me the importance is in enabling refactoring and acting as a programming assistant.
@benhuangbmj
I like how you review the brief history of the evolution of the language and it's interesting to see how those big tech companies joined forces. I am currently transitioning to TS from JS. Appreciate your work!
@VeitLehmann
Flow by Facebook/Meta was/is another competitor adding types to JS without changing the language itself. I liked some parts of it better: no interface, just type, no enums, and at least back when I used it (about 7 or 8 years ago), it could infer unannotated types much better than TS. But with the current state of TS, I don't look back.
@firebout7675
thanks for this video, just wana mention, superb editing too
@boonkiathan
The best part of TS is absolute JS compatibility But That's where a devotion to tooling needed sorely Still messed up today
@judewestburner
Typescript is just amazing. Ive been doing apps with TS since 2015 and the thought of going back is the thing of nightmares
@geoffreykioi8459
Why didn't they just add type safety to JavaScript
@TheZonni
Cute video, yet contains some inconsistencies as more likely you're not super familiar with TS runtime 😀
@nickw656
i remember a while ago, there are a couple of famous projects switched from ts back to js.
@Neckhawker
Native type anotation would be so juge for performances.
@khalidelgazzar
Lessonslearnt: 1. Solve problems one at a time. 2. Even if you solved all the problems, newer ones will emerge. Refer to rule 1 for solving the new problems. 3. If there's common ground to build upon, the unite forces in solving problems.
@DeepSeekAgent301
Typescript compiles in to JavaScript. So, you can not say that someone has replaced javascript with typescript it is just not true
@jf3518
Great Video. TypeScript is what keeps frontend devs sane. It is really nice to write a backend in nodejs with TypeScript and then let the rest API client and openapi docs be autogenerated from the TypeScript definitions. I have written code in lots of language and TypeScript is my favorite. It's expressiveness is just amazing. Golang with TypeScript type system would be unbeatable.
@CodeSource