Because writing Rust backend is needlessly complex for majority of projects.

maccard · 2026-03-13T08:49:19 1773391759

There’s a middle ground between node and rust. Dotnet and Java are wildly productive places to work but they’re not as exciting as rust.

Also, writing JavaScript for the backend is needlessly underperforming for anything with any load.

pjmlp · 2026-03-13T08:24:29 1773390269

Still easier than dealing with node dependencies, webpack and co, they make me wish to write ASP with OCX components instead.

drawfloat · 2026-03-13T08:33:26 1773390806

Your complaint is with Vite – famously incredibly simple and reliable to work with – using Rust, but you're bringing up webpack's complexity?

Node dependencies are fine, add an npmrc file to have it default to exact versioning and you solve 90% of common day to day problems. It's not ideal, but nor is cargo's mystery meat approach to importing optional features from packages.

pjmlp · 2026-03-13T08:36:17 1773390977

My remark, and not complaint, is that the fashion to rewrite everything in Rust across the JavaScript ecosystem proves the point of holding it wrong.

Maybe leave JavaScript on the browser, where it belongs.

drawfloat · 2026-03-13T19:02:17 1773428537

Rewriting build time tooling to Rust is leaving Javascript on the browser?

omnimus · 2026-03-13T21:20:17 1773436817

Somebody just really dislikes JS. I sympathize. I wouldn't (be able to) write backend in Rust though.

pjmlp · 2026-03-14T05:57:45 1773467865

Why stop at tbe build tools, take JS ecosystem out of the backend.

potwinkle · 2026-03-13T08:14:02 1773389642

I've had a great time using Rust with Actix as the framework.