I’ve Got 99 Problems but Learning TypeScript Ain’t One
I asked this question on Twitter last week and got ~100 replies.
Sharing my learnings from the responses, as it gives insight into what keeps developers from migrating to new tech. Even when the alternative is better.
Let’s get into it.
A lot of newbies and beginners gave the “I am still learning JS” response.
Understandably they don’t want to take up more than they can chew at the moment.
Most of them are interested in trying it out in future, whereas some were looking for guidance on if they should.
Developers already working with JS, had a pressing question → “What’s the need?”.
Their motto: “If it works, don’t touch it”.
Sorry, too soon 🕒
Some experienced JS developers have learned TypeScript in plans, but think the right time has not come yet.
Unlike developers who are not willing to migrate, these devs see value in TypeScript. Just that they didn’t get the right project yet, which justifies the learning curve.
Also, they are hoping that tooling (like support for running TS code natively in the browser) will improve in the future.
Well, it depends 🧐
Some developers have spent time learning TypeScript, but don’t use it for every project.
As per them, it’s suited when:
- Working in a team
- Writing production apps
- Codebase is huge
They said “For personal projects and simple apps, TypeScript is an overkill”.
ECMA is getting there 🏁
Lastly, a few responses were about ECMA 6 already supporting enough modernity to write clean code in JS.
Wrapping up 📝
Share in comments your motivation to move or not move to TypeScript?
If you liked this post, you can follow me for more of these.