[Retozi]

I agree 100%.

TypeScript is an invaluable, mature technology that provides large productivity boosts to any team that maintains a mid-sized code base.

It plays extremely well with React too, and it's benefits are independent of the tech stack. If you are used to typed components/templates, you will NEVER want to go back.

I would argue that is more important to have static typing in the front-end compared to the back-end in a web-application context. There is more state, lot's of shared entities and unit tests are expensive to write and maintain.

[gspetr]

> There is more state, lot's of shared entities and unit tests are expensive to write and maintain.

Good point, but only to an extent: Unit tests boilerplate in dynamic languages that is redundant with static typing is only a (minor) subset of unit tests that you should be writing for your code. Static typing is not an excuse to skip unit tests altogether. I've unfortunately met people claiming exactly that...

[gravlaks]

In 2014 I used Typescript on a four month long project. I liked it alot compared to using just JS, however compiling was slow.

I retried using Typescript 1 month ago. Compiling took 6-7 seconds for about 8 files. I could not find a solution and gave up using TS. I hope that's just me doing not good enough research.

[throwasehasdwi]

Definitely something up with your environment. We compile hundreds of .ts files at my job each build and it only takes a few seconds

[eljs]

Must be something with your setup, tsc is known to be quite fast. Maybe try using it with the watcher? "tsc -w" and you'll never need to compile more than one file at a time.