3 ms·
I've used it to moderate success on an 8 month React project. I originally started the project in ES6 and then migrated it over to Typescript. It generally work
by JoeyJoJoJr 8y ago
I've used it to moderate success on an 8 month React project. I originally started the project in ES6 and then migrated it over to Typescript. It generally works well with React, aside from a major pain point which is that it makes it difficult to compose with higher order components.
If you are working in your own bubble with few outside dependancies it works very well. I have been learning WebGL lately, and have found it extremely useful in that regard. Things get hairy dealing with external libraries with often flakey type definitions.
I would still use Typescript on new projects where I can. I have come to accept that I will often just need to use "any" in place of a proper type. There is the temptation to spend a lot of time creating complex types with generics but I've found it to be a can of worms. I'm always looking for new ways leverage the type system, and feel like I often hit dead ends.
Generally I think using Typescript to be an improvement over plain ES6. It catches a lot of bugs, and allows me to refactor with more confidence, but it is very far from ideal.
- 52-6F-62 8y agoThis is generally how I feel as well. I definitely prefer it to Flow