I come from OOP languages and do rust mostly nowadays. > you have to junk the object-oriented design entirely I think it's not this black-and-white. OOP on a

I come from OOP languages and do rust mostly nowadays. > you have to junk the object-oriented design entirely I think it's not this black-and-white. OOP on a higher level is about encapsulation and message passing. Such design is perfectly doable in Rust. I'd say that it's more natural in Rust due to it's `impl` concept: where behaviour and data are coupled in a way that's different from most OOP languages. Who owns which data, and who can operate on it, is something that, in OOP, should be thought about just as well. Java, Ruby, et al make it easy to make a mess from this; yet that doesn't make all OO-design a mess. Ihat really is "bad use of OOP", and no reason to "junk the OO design entirely". At most it's "junk the bad OO design".