3 ms·
For people who have not used TypeScript: I've never had issues with the TypeScript compiler being slow, and I write my types with as much complexity as the und
by smt88 6y ago
For people who have not used TypeScript:
I've never had issues with the TypeScript compiler being slow, and I write my types with as much complexity as the underlying data/situation demands.
I have several projects that consume dozens of REST APIs, and I have types for all of their requests and responses, and my compilation time is still fine.
- simlevesque 6y agoOnly problem I ever had is some weird deep nested graphql autogenerated types. Otherwise it just works.
- DanRosenwasser 6y agoIn chatting with users, I've heard the generated types vary in quality by a lot depending on the tool you pick. Supposedly this one is pretty good: https://graphql-code-generator.com/docs/plugins/typescript https://graphql-code-generator.com/docs/plugins/typescript
- momokoko 6y agoI’ll match your anecdote with my own. I’ve worked with several large codebases in TypeScript and slow compilation is a common problem I’ve dealt with. To the point where some people I’ve worked with specifically chose to work on desktop PCs for the extra CPU. With that said, compilation performance is something most compiled languages deal with so I wouldn’t treat it as some kind of flaw specific only to TypeScript