I’m still learning Rust coming from Python and R and honestly point 2 and 3 are not even that bad. Sure I have been bashing my head against some corners, and the lack of OOP was somewhat unexpected, but imho the language really helps you think about what you are doing.
At its core, OOP is just commingling data and operations, whereas FP is separating data from operations on data. I’m not an expert at Haskell (I cut my FP teeth on Lisp), but that’s essentially what typeclasses look like to me.
The Rust book has a section on OOP, and the main thing to remember is that Rust solves OOP through composition instead of inheritance. Rust doesn’t have inheritance in any meaningful way, but it can solve problems in a similar way as classical OOP.
I’m still learning Rust coming from Python and R and honestly point 2 and 3 are not even that bad. Sure I have been bashing my head against some corners, and the lack of OOP was somewhat unexpected, but imho the language really helps you think about what you are doing.
Rust absolutely has OOP, that’s what Traits are for. It just doesn’t have classical inheritance, so you structure your patterns a bit differently.
That said, I lean more into functional-inspired style anyway, which tends to work pretty well w/ Rust.
traits aren’t oop. they’re closer to haskell’s typeclasses than anything else
At its core, OOP is just commingling data and operations, whereas FP is separating data from operations on data. I’m not an expert at Haskell (I cut my FP teeth on Lisp), but that’s essentially what typeclasses look like to me.
The Rust book has a section on OOP, and the main thing to remember is that Rust solves OOP through composition instead of inheritance. Rust doesn’t have inheritance in any meaningful way, but it can solve problems in a similar way as classical OOP.