3 ms·
Rust is not an "anti-OO" language. It has a basically complete featureset for OO programming with the one exception of implementation inheritance. It is fully
by zozbot234 5y ago
Rust is not an "anti-OO" language. It has a basically complete featureset for OO programming with the one exception of implementation inheritance. It is fully usable for programming "in the large".
- jiggawatts 5y agoYou say that it is fully usable for programming in the large, but other than Servo I can't think of any large Rust projects of the top of my head. Certainly there are none with more than 1K developers collaborating. I'm aware that you can have "dyn Trait" in Rust and a Box of a trait also provides runtime polymorphism. However, it just has too much friction due to explicit "no more OO!" decisions by the Rust core language team to enable truly large-scale programming, at least in my humble opinion. I think such decisions stem from logic like this: "I saw OO used extensively at <insert large project> and the <project> was a huge mess and nobody was happy, hence OO is bad and should be avoided." Meanwhile the logic is more like: "<large project> needed OO because it was large, and it was unpleasant to work on because it was large, not because it was OO. It would have been worse if it wasn't OO."
- deltaonefour 5y agoYou can say this for ANY language. Literally any language that can assign a function to be part of some struct could be "OO"... which is basically any language including C. So given the pervading reality, colloquially when we say the term "Object Oriented Language," we are not referring lisp or C or haskell even though all of those language are technically OO. The same can be said for Rust. Rust is NOT OO.