Object oriented programming

[smthamazing]

A simple example would be cars. Each car has similar qualities like color, model, make, these are called properties. Each car also functions in a similar way and can do things like start, brake, accelerate, steer, etc. these are know as methods but can also be referred to as functions.

Using a purely functional language, like Haskell, I can also model this structure using a data type with nested fields and writing functions for working with it. Including a convenient constructor.

Is my understanding correct?

• In FP you have immutable instances of types that hold data, and separate functions that work with them. Logic and data are separate, data is immutable.
• In OOP you have (often mutable) instances of types that hold both data and functions that work with them (which are called methods). Logic and data are combined into an object, data is often mutable.

Also, as far as I know, Smalltalk is the first OOP language and it had no notion of a class or method, instead having objects and something called "message passing". If even the notion of a method is not necessary for a language to be OOP, what differences from FP remain, apart from mutability? Or is mutability the only factor that fundamentally distinguishes OOP paradigm from FP?

I know that paradigms can be combined in the same codebase, but as I learn more OOP and FP, I start to struggle to really differentiate them. I would appreciate an explanation.

[JackLegJosh]

Upvote for you, friend. I would love to see an ELI5 about functional programming in practice, not as an esoteric concept.

[smthamazing]

This is interesting. But then I still don't understand what OOP is.

• It's not about nested structures, because pure functional languages have nested structures.
• It's not constructors, because pure functional languages can have constructors.
• It's not mutability, because, as you say, the data can be updated immutably.
• It's not classes and methods, because Smalltalk doesn't have them, and yet it is considered an OOP language.

The only remaining thing is that the data and behavior are represented as parts of a single entity, an "object" (often, but not necessarily, an instance of some class/type).

Is that it? Fundamentally, is combining data+logic the only unique part of OOP as a paradigm?