Hacker News Reader

Comment by pjmlp | Hacker News Reader

With all the RIIR going on nodejs ecosystem, I am waiting for the blog posts on how people completely got rid of nodejs, rewriting the whole backend in Rust and how everything is so much better.

Waiting for Show HN: AbrasionNext, the framework evolution for frontend devs, with SaaS cloud deployment.

View on HN

It seems Rust "just" needs RoR level web framework and Qt level GUI framework to take over the world, everything else is already conquered (with some Go conclaves still holding on).

"It seems Rust "just" needs RoR level web framework"

its already HERE https://loco.rs/

I writing a production level app right now with it

> Qt level GUI framework

Trying to bring that with Slint: https://slint.rs

> RoR level web framework

This is not happening. The new folks have moved to SPA/RSC and a RoR type framework doesn't make much sense in that context.

Elixir/Phoenix is doing great

> I am waiting for the blog posts on how people completely got rid of nodejs, rewriting the whole backend in Rust

I did this for several projects, works great with much lower costs and compute/memory usage.

This is one of the most ridiculous RIIR I've seen.

It's a CLI tool that makes API calls. I'd bet my bottom dollar that the performance difference between API-wrapping CLI tools in something like Ruby/Python vs Rust/C++ is negligible in perceived experience.

If they wanted people to not have a dependency on Node pre-installed, they could have shipped Single Executable Application's [0] or used a similar tool for producing binaries.

Or used Deno/Bun's native binary packaging.

[0] - https://nodejs.org/api/single-executable-applications.html

Having the CLI self-contained and easy to cross-compile is a huge improvement, as is the binary size (from what I've seen, wrapped Node binaries are huge). Also, a CLI tool should have low latency and no matter how good your engine is, an interpreter will have much higher startup latency than a proper binary.

It's not just API calls though.

It's often parallel processing of I/O (network, filesystem) and computational tasks like testing and compiling code.

These tools just run the test/compile commands in a shell…

Reply on news.ycombinator.com