I've been playing with writing my app project in Rust. It has an obtuse learning curve, partially created by inconsistent syntax that you eventually learn. This would be things like type path having the scope resolution operator being optionql while it isn't for the path pattern and generic args vs where clauses and why you should choose one over the other.
It's Rusts proc macro implementation that has the biggest sets of inconsistencies that I think hold the language back. The is a proc_macro create and a proc_macro2 crate. The built in token parsing is extremely basic, the helper libraries like syn are not flexible for custom syntax, like a path argument. Furthermore, you ideally understand the odd parts of the language because procmacros are just s token parser.
One last concern of there is no name spacing of packages, meaning it is harder to tell if you are installing packages from a trusted author.
While I like Rust, the ergonomics don't match the deeply thought out patterns of languages like Typescript or Go.