This is why TypeScript is worth looking into
In the end, you will be able to submit higher quality work, as TypeScript has already found a lot of mistakes along the way that you do not need to run the program to detect. And you can work faster, more efficiently, and with greater confidence that things get right.
In StackOverflow's survey 2016, TypeScript came one in response to the question "Which technology would you prefer to use?". It is remarkable for a language to climb to first place in just a few years. It shows little that there is a real need for TypeScript; that you see the value.
Okay, but what's the chin? Why do not all TypeScript use? Are there any disadvantages?
I've heard that using Flow instead. Is it true?
Flow is an interesting option with about the same selling points as TypeScript. (Flow is developed by Facebook and TypeScript by Microsoft. Both are open source.) However, it is quite clear that TypeScript has "won" in the sense that it has a large community and lots of support from all directions. A little like the situation with Git and Mercurial; The latter is a good alternative, but it has a significantly smaller market share.
You have done a course for people who want to know more about TypeScript?
News & feeds
Brushing teeth and static checks
The three-year-old at home doesn't like having his teeth brushed. But I, a crafty father, have developed a trick.Read more >
CSS selectors are evil and JS is the solution
A pragmatic demonstration of the drawbacks with CSS selectors, and how inline styles through JS solves these problemsRead more >
Top 5 Podcasts during Christmas
We at Edument would like to thank you for this year and wish you a Merry Christmas and a Happy New Year with our top 5 Podcasts list!Read more >
Invariants hidden in callbacks
Callbacks might look simple and innocent, but they can be dangerous!Read more >
What it means to boldly go where you have never been beforeRead more >