Re:Rust 1.17
by epage on Thursday April 27, 2017 @03:09PM
(#14213932)
Which languages are your point of comparison? Its a different conversation to have to talk about C, C++, D, Swift, Nim, Crystal, or Julia?
Which ergonomic issues are your main concerns?
Some things I can think of
- Libraries focusing on optimal performance over ergonomics
- Lifetimes
- Results not being quite as ergonomic as exceptions
While it has rough spots now, I'm hopeful for the future.
The impression I've had watching Rust's evolution is they want to push the language to its limits, find the weak points, find ways of fixing it, and repeat. They don't want to speculatively throw in features. For example, we started off with try!() and later got .?.
Improving the documentation would also improve people's perceptions. I've gone through waves of feeling like Rust's error handling is close enough to the ergonomics of exceptions. When I had surface knowledge, it seemed great. I then started using it and running into problems. I then came across random blog posts and it became easy again.
Which ergonomic issues are your main concerns?
Some things I can think of
- Libraries focusing on optimal performance over ergonomics
- Lifetimes
- Results not being quite as ergonomic as exceptions
While it has rough spots now, I'm hopeful for the future.
The impression I've had watching Rust's evolution is they want to push the language to its limits, find the weak points, find ways of fixing it, and repeat. They don't want to speculatively throw in features. For example, we started off with try!() and later got .?.
Improving the documentation would also improve people's perceptions. I've gone through waves of feeling like Rust's error handling is close enough to the ergonomics of exceptions. When I had surface knowledge, it seemed great. I then started using it and running into problems. I then came across random blog posts and it became easy again.
For a further discussion on documentation, see https://www.reddit.com/r/rust/comments/67fb8e/rust_tribal_kn...
The next step is creating ergonomic libraries. ezstring is an example of people experimenting with this.
ezstring: https://github.com/Storyyeller/easy_strings