Hacker News new | ask | show | jobs
by 0xFACEFEED 1759 days ago
My guess: Deno would perform too slowly which would hurt the UX. It would also be harder to maintain than a language like Rust. And of course Rust doesn't need a runtime.
1 comments

I think you nailed it!

If Deno wouldn't use itself because of reasons like this; then people should really think twice before using it to build anything server side.

Not everything is about performance. Deno lets developers be more efficient than Rust, and it is easier to hire developers that already knows TypeScript/Node.
How is Deno more efficient?
If you're building a application on top of PostgreSQL and GraphQL then there's no Rust equivalent to PostGraphile, which is a JS/TS lib.

If you're building on top of GCP services, there are official JS/TS libs but no official Rust libs.

If you're doing data science then the ecosystem of Python libraries (another interpreted language) will get you up and running much faster than Rust.

So yes, there are plenty of cases where using an interpreted language will be much more productive than limiting yourself to Rust.

They mean more efficient for the developer not the machine.