Hacker News Reader

Comment by stephen | Hacker News Reader

Amazing. This is what the Typescript team should have done instead of rewriting to golang -- innovate the runtime.

That doesn't help anyone using Node. I don't want to have to start using a new runtime because my compiler is slow. That's wild.

You're already using a new runtime with tsgo -- it's golang at build time -- but still running Node in prod, so the same could work here. :-)

Agreed I would not want all Typescript users forced to use /this/ runtime, but if the TS team shipped tsc as "oh now it's uses a special fast JS runtime" (just like tsgo is a different runtime) I'd love to at least have the option of using the same special fast runtime in my own still-written-in-TS apps.

Seems I've either struck or a nerve, or miscommunicated, given the insta down votes.

if there was a thingy that compiled JS to a 10mb native executable with shared heap multithreading, im sure we'd use it. however, no one has invented such a thing. until this pr.

Right! That's why I think this is an exciting development.

I assume everyone is downvoting me for "liking LLM slop", but really I just like the competition that "this is possible!"

And would love a slop/non-slop/whatever version in Node/v8. Someday!

same. ts with thread + struct would be a killer language.

i pray anthropic buys roblox to get pizlo to actually land this

tsgo isn't loading a full js jit compiler and a significant subset of the Node standard library. I'd be equally upset to see a Python compiler installing Pypy as a performance improvement to compile code for CPython faster.

Reply on news.ycombinator.com