Hacker Read top | best | new | newcomments | leaders | about | bookmarklet login

I truly do not understand this Rust-for-all-problems mentality.

I was under the impression that Rust was essentially the next generation of C, meant for things like compilers, embedded systems, and other places where memory truly matters.

Why are we shoehorning it into things like REST APIs and frontend frameworks? One look at that syntax and I'd think anyone could see it's not the right tool for the job, even if there room for disruption in those spaces.



view as:

Believe it or not, there are REST APIs and frontend frameworks for almost every programming language under the sun. And I mean EVERY. Example: this Prolog works in your browser https://github.com/SWI-Prolog/swish, and this is the corresponding package to do the API https://www.swi-prolog.org/pldoc/man?section=http-running-se...

But I can agree Rust has better marketing than Prolog.


+1. I’m all for using the right tool for the job. It seems like all these technologies are to cater to specific niche of engineers and that’s the exact reason why they don’t have the longevity.

Legal | privacy