I'd say you're feeling friction, which makes sense, but that doesn't mean this is a hard and fast rule.

In the C++ vs Java fight you might have cases where you need to be fast, and C++ (with sufficient optimizations) might make your program much faster. Then again I'd pick C or Rust if I started a new project (C, because it's much more manageable, Rust because it has a lot of the useful C++ features while maintaining memory safety). But then Rust might a Spanish Prison Guard, it takes effort to learn. There is notable friction when you first encounter the borrow checking compiler. The payoff is big though (trust me, or better check for yourself).

I agree with your thoughts. To clarify, when using the term “friction”, I wasn't referring to a learning curve. I'd also consider learning (more) Rust energy well spent, until proven otherwise.