3 ms·
> As a node developer writing pure none-compiled JavaScript, my run time is extremely fast from changing code to seeing its results. It takes milliseconds for m
by mrkurt 6y ago
> As a node developer writing pure none-compiled JavaScript, my run time is extremely fast from changing code to seeing its results. It takes milliseconds for me to run brand new code in my terminal.
Deno runs JavaScript faster than node:
echo "console.log(1 + 2)" > not-ts.js
time deno run not-ts.js
3
0.01s user 0.01s system 89% cpu 0.025 total
time node not-ts.js
3
0.03s user 0.08s system 53% cpu 0.203 total
> Since it's not even native TypeScript, it's just embedded the tsc which builds and caches the compiled code, why not let TypeScript developers add their bundling pipeline in the same way as they've always done.
You can!
- turblety 6y ago> Deno runs JavaScript faster than node Yup, and that's really cool and exciting. My issue isn't with runtime timing. That's not what costs me money. Developer time is what costs money, and every change having to "recompile" my already raw JavaScript costs way more than saving 0.02s at runtime.
- jon889 6y agoCan't you just pass it a .js file and it will skip the TypeScript compiling completely?
- turblety 6y agoHaha, yup. Thats much better. Thanks!
- mrkurt 6y agoHaha that's what I was trying to demonstrate!
- NoInkling 6y agoThat's not gonna help if you're using any part of the standard library though (or presumably most 3rd-party modules), since it's written in TS, right?
- chrischen 6y agoI'd assume you can just use regular node modules in that case?
- silverwind 6y agoI assume their TS parts will be pre-compiled, at they should be.