TypeScript has turned six today, and I would like to take some time to reflect on what this amazing technology has meant to me at a personal level ...
For further actions, you may consider blocking this person and/or reporting abuse
Hi Remo. Thanks for the post to share your experience and helping the TypeScript community.
Context: I haven't used TypeScript but proficient in C#.
I have been using C# since .NET 2.0 and been able to keep up to C# 7 as the change was gradual.
Would you be able to share how to get started with TypeScript for someone who've never used TypeScript?
(I feel a bit overwhelmed since TypeScript is so mature & I will feel the same way with C# should I start again from scratch).
I just converted my JS frontend to TS frontend. I've learned a lot about TypeScript during this process. Also, TypeScript has wonderful tooling! I love how well VS Code integrates with TypeScript, providing code completions and such (yeah I know both of them are born under Microsoft, so they will work together pretty well, but still!)
So you can start converting a component written in JavaScript to TypeScript one by one?
Are there any interop issues? TYpeScript component not being able to call components written in pure JavaScript, vice versa.
Yes.
No, AFAIK. You can use your pure JS components and libraries.
Thanks Defman 🤜
Thanks for the feedback, I will think about it and try to put something together.
Install VScode and ts-node, then simply run ts-node in place of node for any .ts file. Make sure you have a tsconfig.json and tslint.json file as well and refer to TypeScript’s getting started page.
I just released ladder.ts.training/ it might help you during the learning process :)
Thank you Remo for the curated list of TypeScript learning resources 😀
🤜
This is purely a coincidence that I started learnt typescript yesterday from Dylan, and started converting some of my early-time projects today. This is awesome 🎉
Agree with this feeling, I get it when dealing with statically-typed programs. It's a little hard to explain, but your mind starts to think in a set of logical pathways through the code, like a type-checker, instead of like the value-level reasoning it normally does.
Hillel Wayne has said this about TLA+ too (he wrote a book called Practical TLA+), that he can look at an algorithm and the concurrency bugs in it leap out at him.
I think it's something like the Sapir-Whorf hypothesis, where your language determines your thought patterns.