> Yeah, except not every business is willing to wait 25 years for Rust to achieve parity with today's Java ecosystem. Unfounded speculation. You've made this n

> Yeah, except not every business is willing to wait 25 years for Rust to achieve parity with today's Java ecosystem. Unfounded speculation. You've made this number up. > Rust IDEs can't still offer completion that works all the time, let alone all the other IDE features I didn't see any problems in IntelliJ. If there are cases where autocomplete doesn't work, these are rare edge cases and they don't affect predictivity. VSCode was a bit laggy, but that's probably VSCode problem not Rust's. This is what happens if you base a desktop tool on a browser running JS. > Rust's has a big selling story for OS low level systems libraries It is good at that, but this is not the primary reason to use Rust. Rust selling point are explicit lifetimes which make it virtually impossible to create pointer hell I found in every commercial Java codebase I worked on. It is the same level of productivity enhancement as introducing static types over dynamic. Explicit lifetimes make it a bit harder to write in Rust but code is being read 99% of time and written only 1% of time.