4 ms·

I think that its a reflection of where much of the market's jobs are: "backend web app" might as just well be replaced with "thing moving data around with RPCs"

I think that its a reflection of where much of the market's jobs are: "backend web app" might as just well be replaced with "thing moving data around with RPCs" which is what so much of the value software provides in the economy is tied up, these days. Also, for startups who live-or-die by their cloud hosting costs, reducing CPU utilization by 2x and MEM utilization by 5x versus GC'd languages, the value proposition is real.

Thaxll 7y ago
That's not how it works, since most startup run python / ruby / nodes code, the cost of your app is definitely not a big concern, especially since you can have performat code in any language, you don't need rust speed in 99.9% of the cases.
- steveklabnik 7y ago
  It’s not always about performance. Memory usage matters too. And reliability. We’ve heard all of these things from folks switching.
- nicoburns 7y ago
  Sometimes performance matters. At my previous company we settled on a Rust solution for one component (ingesting analytics data) after cycling through python and node prototypes that were just too slow (we had 100+ GB of data to process, and the node.js app was taking 15 minutes to process one 500mb file). And once the data processing code was in Rust, it made sense to have the endpoint that collected the data in Rust too. It would probably have been possible to optimise the node/python versions. But it was easier to write it in Rust that is designed for these high-performance scenarios. An unexpected bonus was just how reliable our Rust code turned out to be. I'd definitely consider Rust for non-performance critical code on that basis.
- Dowwie 7y ago
  Performance is the tip of the value proposition iceberg for Rust.