TypeScript has gained a lot of popularity since the Angular 2 project decided to adopt it and write all their documentation examples in TypeScript, but is it really worth the investment?
Before we get into this, I’ll preface it by saying that I’m a fan of the tools that static types enable, and TypeScript is currently my favorite static type system for the JavaScript community.
I come from a background using statically typed languages including C/C++ and Java. JavaScript’s dynamic types were hard to adjust to at first, but once I got used to them, it was like coming out of a long, dark tunnel and into the light. There’s a lot to love about static types, but there’s a lot to love about dynamic types, too.
I’m not religious about tech stacks and dev tools. I’m practical. I do consulting, and a lot of dev teams use Angular 2 and TypeScript these days. If I’m going to give them advice, I’d better know what I’m talking about.
I strongly recommend that you adopt a similar open-minded attitude towards new and different tech stacks and tools. Believe me, you’ll learn more than a few during your career.
Being a developer means that you’re choosing a lifetime of learning new things. It’s a good idea to make peace with that right now. That doesn’t mean learn all the new things, but do be open to new things if you need to learn them for your work, or just the joy of discovery.

