undefined | Better HN

0 pointspjmlp13d ago0 comments

Why go halfway, embrace compiled languages in the backend.

Fast all the way down, especially when coupled with REPL tooling.

0 comments

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

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.

pjmlpOP13d ago

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

drawfloat13d ago

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.

1 more reply

potwinkle13d ago

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

wiseowise13d ago

It takes tooling team and discipline to keep compile times at bay when you reach mid size projects with compiled languages (looking at you Java, C++, Rust).

christophilus13d ago

But, it doesn’t need to be so. Go is pretty fast to compile. So is Jai, from what I’ve seen. So was TurboPascal. Rust has a similar problem to the one Vite has been solving- Rust (and most languages) weren’t designed for compilation speed, and it’s hard to retroactively fix that. But, there’s no reason we shouldn’t have a bunch of statically typed, fast-to-compile languages.

pjmlpOP13d ago

I agree with your remark, only that Rust's current problem is tooling, not the language itself.

See OCaml or Haskell, they also have interpreters and REPLs as part of their tooling.

Also there should be no need to always compile crates from scratch when starting a new project.

Which ironically circles back to your remark of having a similar problem.

pjmlpOP13d ago

Lack of discipline is exactly the magic word regardig the node ecosystem mess.

wiseowise13d ago

Maybe? The point still stands that majority of programmers/industry is not equipped to deal with this adequately.

j / k navigate · click thread line to collapse

0 comments

omnimus13d ago

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

maccard13d ago

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.

pjmlpOP13d ago

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

drawfloat13d ago

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

1 more reply

potwinkle13d ago

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

wiseowise13d ago

It takes tooling team and discipline to keep compile times at bay when you reach mid size projects with compiled languages (looking at you Java, C++, Rust).

christophilus13d ago

pjmlpOP13d ago

I agree with your remark, only that Rust's current problem is tooling, not the language itself.

See OCaml or Haskell, they also have interpreters and REPLs as part of their tooling.

Also there should be no need to always compile crates from scratch when starting a new project.

Which ironically circles back to your remark of having a similar problem.

pjmlpOP13d ago

Lack of discipline is exactly the magic word regardig the node ecosystem mess.

wiseowise13d ago

Maybe? The point still stands that majority of programmers/industry is not equipped to deal with this adequately.

j / k navigate · click thread line to collapse