You literally just got a user experience report claiming that it is.
There's no winning over everyone. Of course Rust's syntax will be completely jarring if you're coming from Crystal or Ruby.
In my personal experience it's a little jarring at first and then it completely goes away.
* The need to put :: before <> in expressions for generic parameters, but not in type signatures.
* Using :: instead of just . even though most of the time the naming convention will delineate the difference anyway
* Error handling with futures
* Self-referential structs
* Passing a shared pointer through multiple move closures
IMHO the frustration involved in these things is not typically worth being more explicit. The :: thing may seem a bit pedantic, but it is simply more physical effort (Shift-colon-colon vs dot) and creates more visual noise.
If/when all of the things above are addressed, I think Rust could give Python a run for its money.
I don’t mind the syntax because I find it explicit enough, but terse enough in certain cases. It’s similar but different and so it rhymes with my past in C++, but it’s not the same.
Rather, I think the problem is that the syntax is 100% fine in isolation, but has some issues when taken together with experience in other languages — when you skim the code, some parts of it beg to be looked at like C++, while other parts push you to read it like a functional language. Unsurprisingly, neither fully works, which makes the experience jarring. Once you accept that Rust is its own language with its own rules and stop trying to borrow (hah!) from your experience with other languages, it feels much better.