This comment in the Jest repository, https://github.com/facebook/jest/pull/7554#issuecomment-454358729, has been floating around on the Twitterverse the past few days and seems to be garnering a lot of attention.
Other prominent JS devs have been chiming in as well. Some with a little more cursing, so apologies in advance. 😉
I've been using TypeScript for ~1 week now. Migrating from Flow.— Kent C. Dodds (@kentcdodds) December 20, 2018
Breath. Of. Fresh. Air.
I'll blog about this in a week or two. This is really great though.
Side note. TypeScript is taking over. It has gained rapid adoption in 2018 and its embarrassing that I don't know it.— Ryan Florence (@ryanflorence) October 30, 2018
If you're looking for a job, there's a 50/50 chance your next code base will be using it if my workshop attendees are any sort of decently random sample.
TypeScript: will cement the role of raw JS as a prototyping language, and give it a certain incremental path towards increased safety, correctness, enhanced team collaboration. ".ts" will be supported out of the box by most frameworks and platforms. Bonus: https://t.co/vuSQFdVNsG— Guillermo ▲ (@rauchg) December 29, 2018
Is this the final nail in the coffin for Flow? Is it another year where TypeScript adoption continues to rise and it becomes the Year of TypeScript?
There's even a horse_ts Twitter account now. It's not too hard to guess who it is, but I still find it pretty funny.
"So if you’ve been a holdout (like me, to be honest), 2019 is definitely the year to learn TypeScript.", KBall quote from https://zendev.com/2019/01/15/frontend-development-topics-to-learn-in-2019.html
Share your thoughts on the mirrored post on dev.to
And while you're here check out my older post Consider Using TypeScript