Hi Paul.

Simplistically it’s a reference to different code organization an encapsulation between OO and FP.

OO tends to put behavior and data (i.e. the object’s internal state) together in the class — objects are passed a message that may contain data, which may or may not return a result but may update internal state. In many OO programs, this internal state is often mutable (but not always).
FP tends to build general functions that operate on data — functions are passed data to manipulate and return a result. There is no state in the function that survives beyond the call. In many FP programs the data are immutable (but not always).

Obviously OO/FP hybrid languages like Scala and F# can combine these approaches.

Static or class methods in an OO language (usually in some “utility” library) can provide a similar experience in that they often separate the data (in your object) from behavior (in the utility method). If the OO language also supports lambdas then you can get an even closer experience with the use of higher-order functions (those that take other functions as arguments). Similar, but not quite the same

Thanks for the question!
Josh