Rust programming language is often viewed as the successor to C/C++, poised to eventually dominate the development of safety-critical kernels and low-level applications. It holds holds significant potential in API layers.
I agree. I have written server software my entire career, and the need for performance is a corner case in my experience. The never crash in runtime aspect of rust should get much more attention (I know it can panic, but that really never happens in practice unless you use unwrap or smilar).
It’s pretty interesting for microcontrollers, kernels, and other types of low-level applications.
That said, I agree. I’m more interested in provable memory safety and certain forms of correctness guarantees. I’d love to see more work on pure functions and other FP concepts.
I wish people would focus less on the performance. Performance is the least interesting aspect of Rust.
I agree. I have written server software my entire career, and the need for performance is a corner case in my experience. The never crash in runtime aspect of rust should get much more attention (I know it can panic, but that really never happens in practice unless you use unwrap or smilar).
It’s pretty interesting for microcontrollers, kernels, and other types of low-level applications.
That said, I agree. I’m more interested in provable memory safety and certain forms of correctness guarantees. I’d love to see more work on pure functions and other FP concepts.
As someone in Java land, performance is not impressive because anything can beat it. It will take features and stability to get people to migrate.
I probably will not be one of the early adopters, but I’m always excited to see what’s out there to contend.
As someone in Java land, you might be more impressed about its memory footprint rather than its performance.
Your Java hello world that takes 4GB of JVM heap space or it will fail with OutOfMemory would likely be only a few mb in Rust (or even less)
Haha, I’m well aware.