Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I've poked around in the TypeScript codebase just a little bit, and it's clear they've squeezed as much performance out of JS as they can (though really, you can tell that just by using the thing; it's impressively fast even though it's still "slow"). It's funny to see stuff like bit-flags in a JavaScript codebase

I am a little surprised nobody at Microsoft has started working on an official native compiler (or maybe they have, and we just don't know about it yet). It does feel like they've hit a ceiling



One of the core goals of TS is that it has to run in browsers, a native compiler is just not a good goal and it is not in the roadmap.

I think WASM is still not a good fit for a typechecking server.


I wasn't aware of that as a core goal. Do you have a reference where it's stated?

I also don't see why WASM wouldn't be a good fit for that


The core metric for TypeScript's success was to be able to put an IDE in a browser able to run and compile TypeScript itself, which is what the TypeScript team did with the Monaco (and Visual Studio Code) editor in 2011.


Monaco is just the GUI, it doesn't require language support (and in fact, the LSP that was pioneered alongside it means you don't even have to run the language support on the same machine, much less in the same codebase)

Again- any references for this claim? Genuinely curious if this is part of TypeScript's known history, or if it's just speculation


It does exist, for other purposes though, and only targets a subset.

https://makecode.com/language

It compiles to native code via C++.


It does exist, for other purposes though, and only targets a subset.

https://makecode.com/language

It compiles to native code via C++.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: