Hacker News new | ask | show | jobs
by tp_13 2294 days ago
A lot of Rust advocating here lately. But most miss the point. Nobody doubts the performance, efficiency, packaging solution or language design of Rust.

A more interesting question is:

As a CTO: Why would or wouldn't you choose Rust over Java, Node or Go?

Rust is not a new language (started in 2006, 1.0 Release in 2015). Why is its adoption kind of disappointing compared to its technical value?

The answers are not even more benchmarks or another even more wicked zero cost abstraction async runtime.

I'd like to read stories about some real world adoption. Can your average Java or Go devs become proficient in Rust in a reasonable amount of time? Is the code really mostly maintaince free, once it has compiled? Would it have been cheaper to just add some more servers to handle the load? How about large teams working on large domains (Java land)?