That's an overly pessimistic interpretation of the survey. :D<p>With soon to be released "Rust 2018 Edition", quite a bit of mechanism are even easier to use on day to day basis.<p>I suspect that a lot of people that "can't get into Rust", are just bringing a baggage of OOP habits. I suspect it, because Rust (or rather struggles to structure my Rust code), were the main catalyst that made me fully realize why and how OOP is terrible and was causing my problems all along, even before Rust.<p>In a language like Java you can get pretty far, producing a typical OOP mess: with object referencing each other at will, creating a total spaghetti (graph of objects), full of race conditions, terrible performance, objects not being freed for weird reasons, race conditions, unclear ownership semantics etc. You only hit a wall much later, when it's no longer possible to grow or even maintain your terrible, buggy codebase, that was supposed to be so pristine and great, because you followed all the OOP-best practices. But until that wall, you feel quite productive, designing your classes and class hierarchies, and feeling great about yourself.<p>In Rust, compiler demands proof that your code makes sense and is well structured, with clear ownership relationship, lack of race conditions etc. Like any data-oriented paradigm, that is a death blow to a typical OOP approach. People start playing with `Rc<RefCell<T>>`s and then give up, and think it's Rust's fault. I've seen topics like that on r/rust and elsewhere, so it makes me belive it happens quite often.<p>Just to be clear: I'm not saying that there are no other reasons that are going to make it a challenge to get into Rust. But IMO, OOP habits are single biggest mistake, and you must leave them at the door when approaching Rust.<p>IMO, some data-centered development paradigms should be a common part of Rust introduction. A lot of people in the industry are clear that OOP is trash, but because of inertia it is still the dogmatic and popular way that common-developer things about designing software.<p>More on the topic of why OOP is so bad, and what to do instead: <a href="https://dpc.pw/the-faster-you-unlearn-oop-the-better-for-you-and-your-software" rel="nofollow">https://dpc.pw/the-faster-you-unlearn-oop-the-better-for-you...</a>