6 ms·
If you're just porting the code to a new language, the process can be significantly faster than writing it from scratch. But if you're also re-interpreting the
by muglug 4y ago
If you're just porting the code to a new language, the process can be significantly faster than writing it from scratch.
But if you're also re-interpreting the code, which seems to be Donny's approach, you can get bogged down with the discrepancies. The more the two diverge, the harder it is to debug discrepancies and keep track of updates in the upstream code.
I'm also porting a static analysis tool from an interpreted language to Rust, but it's a fairly straightforward port and I've been able to stick to schedule pretty well.
- tuyiown 4y agoThere is also the scenario that tsc is really not that good, and the discrepancies are not a problem enough to avoid potential stc benefits. This can eventually phase out tsc in typescript altogether, the core typescript team making stc the official implementation. This is especially credible with rust having good support with wasm, keeping the js runtime compatibility of tsc.
- cardanome 4y agoWould that be a wise career choice for the people currently working on tsc? Sounds more like they should purposely break compatibility form time to time to prevent Donny from catching up.
- rk06 4y agoShould people really make their professional decisions based on future career choice? I think not. Besides, such malicious action can easily be counterproductive. People can just stop using tsc and switch completely to Rust version. Then, it would effectively make any development on tsc useless.