It's two different concepts. 1) hard to learn 2) hard to read/understand
I would argue rust is hard to learn, and not hard to read or understand once you know it. In my opinion, for example:
Hard to learn, easy to read: Rust
Easy to learn, hard to read: Perl
Hard to learn, hard to read: C++
Easy to learn, easy to read: Python
Even if you don't agree exactly with my opinions, you could maybe see the distinction between (easy/hard to learn) and (easy/hard to read, once you learned it).
I also think that 99% of the difficulty in learning rust is learning how to get to a compiled state. Once the binary is built, you can make a lot more assumptions about it than other binaries (for example, locations of crashes, overflows, ownership, memory freeing can all be detexted). Compare that to c or c++ where getting to a compiled state is way easier, but the resulting binary segfaults or other issues.
I would argue rust is hard to learn, and not hard to read or understand once you know it. In my opinion, for example:
Hard to learn, easy to read: Rust Easy to learn, hard to read: Perl Hard to learn, hard to read: C++ Easy to learn, easy to read: Python
Even if you don't agree exactly with my opinions, you could maybe see the distinction between (easy/hard to learn) and (easy/hard to read, once you learned it).
I also think that 99% of the difficulty in learning rust is learning how to get to a compiled state. Once the binary is built, you can make a lot more assumptions about it than other binaries (for example, locations of crashes, overflows, ownership, memory freeing can all be detexted). Compare that to c or c++ where getting to a compiled state is way easier, but the resulting binary segfaults or other issues.