3 ms·
The obvious solution is for Microsoft to hire him and support the Rust version as a first-class typescript compiler, no?
by zellyn 4y ago
The obvious solution is for Microsoft to hire him and support the Rust version as a first-class typescript compiler, no?
- namuol 4y agoMaybe as an experiment. If it means sacrificing velocity, I don’t think it would ultimately be “blessed” by MS. Perhaps a better way MS could contribute is to define a formal specification for the type checker, which would make efforts like this a lot easier. But these aren’t mutually exclusive.
- xiphias2 4y agoIf the compiler team already spends a significant time optimizing the compiler, the difference in velocity may be not that much. Achieving 100% compatibility on public code bases and switching is a great strategy at this point.
- epolanski 4y agoTwo compilers would be mostly a source of issues and reduce TS velocity. All of that for what, slightly faster compilations? TS server is already fast enough for me to develop giant ts codebases in codespaces on 2 vCPUS with 4 GB of ram.