|
|
|
|
|
by selfmodruntime
1299 days ago
|
|
Now that is a good example. I've encountered the problem of compile times myself. I've asked Daniel Rosenwasser about reimplementing the TSC compiler in a compiled language for a better speedup, but he said it wasn't worth the hassle because the compiler moves so fast and the spec is pretty vast at it's current state. > type errors may be such a small proportion of your errors that a using a type checker isn't justifiable This is a bit biased. The major advantage I see in using typescript is that you can be certain an interface is exactly what it says it is. > As an aside, at least to me your posts are coming off as really combative in this thread You are correct in this. Sorry. I will fix my comments to come off as less abrasive. |
|
Oh super interesting! I wonder if the solution is like, tsc becomes a reference compiler. I'm pretty sure people would absolutely love a Rust implementation that was fast but a little behind. A lot easier to daydream about than to do though, haha.
> This is a bit biased. The major advantage I see in using typescript is that you can be certain an interface is exactly what it says it is.
Yeah and I do miss this in dynamic languages. Interfaces (and typed data structures) have great descriptive power just on their own. There are run time packages for this (prop-types, etc) but... run time is worse haha.