In any problems it is better to use TypeScript?

Do I have to know him to Pontedera?
June 10th 19 at 14:40
3 answers
June 10th 19 at 14:42
Do I have to know him to Pontedera?

No. Do not have. After came ES6+ and became popular the normal Assembly with the linters and tests, the number of raisins in TypeScript markedly diminished, and nowadays its use has become a matter of religion (we need more strong typing or not) and personal preferences. Learn pure JS, but if you at some point feel that you need TypeScript is or will be on the team, where it is used for a couple of days to figure it out.
June 10th 19 at 14:44
In any problems it is better to use TypeScript?

In all, except a short one-off scripts. The larger the project, the more visible its advantages.

Do I have to know him to Pontedera?

In the same measure in what is necessary to know SASS, Less, Pug, JSX.
June 10th 19 at 14:46
If you have a large code base
When the code base is huge, and more than one person working on the project, the type system can help to avoid many common mistakes. This is especially true for single page applications.

When the developers of your team have become accustomed to statically typed languages
Typescript substitute for a Babel
When a library or framework recommend Typescript
When you really feel the need for speed
if(typeof name !== ‘string) throw ‘Name should be string’

With Typescript we can eliminate many of these types of checks all together.

Find more questions by tags TypeScriptJavaScript