3 ms·
That’s fair but - I replaced node with bun a few months ago and I haven’t looked back. All my JavaScript projects run with no changes. Performance is on par or
by josephg 2y ago
That’s fair but -
I replaced node with bun a few months ago and I haven’t looked back. All my JavaScript projects run with no changes. Performance is on par or better compared to nodejs. It can run typescript directly without needing to be compiled. It also has a built in bundler & minifier (bun build), and some other goodies. The command line is a bit different - you need to “bun run” to run scripts. But eh.
Nodejs still works fine, of course. But being able to run typescript directly is killer.
- croes 2y agoWasn’t the USP of deno the baked in security features? How are bun and nodejs on that side?
- nicce 2y agoBun has segmentation faults regularly if you look issue tracker. Security is not there yet.
- andrewmcwatters 2y agoI get the point of Deno's sandboxing, but at the same time, like, imagine writing software and not knowing whether your own code is secure because you're that reliant on downstream dependencies and have to update frequently because your dependency authors are constantly releasing enough that you have no confidence to say otherwise. It's just straight up not a problem other authors are thinking about regularly in other programming languages, because we don't have left-pad crises in other programming language ecosystems.
- curtisblaine 2y agoNode.js supports typescript out of the box by stripping types since node 22 (current LTS is 24, iirc) https://nodejs.org/en/learn/typescript/run-natively https://nodejs.org/en/learn/typescript/run-natively