The worst thing about Java is, that it created a generation of coders, that think OOP is the opposite of FP.

They think that OOP is opposite to everything else

Correction: That don't even know what FP is.

With all things wrong with Java (like its OOP not even being good OOP), I think you can't blame it for this one. The misconception that OOP and FP are irreconcilable opposites is older. And with Java introducing FP concepts (while yet again poorly) it does show the opposite.

Please explain how they're not different? (I mostly write OOP (PHP) but I'm not as familiar with FP so its also an educational question 😄)

...

I think that OOP and FP can and should be used together.

... I don't get the medium article at all.... For me it's like: Hey let's throw complete bogus non practical examples without any depth at the reader. Garnish it with some Wikipedia .... And done.

?!!

I guess it's time I start calling my way of programming 'ACSANSWP'

Applying common cense as needed, simplicity when possible.

@Demolishun
The core of OOP is about grouping data and functionality and producing interchangeable and reusable components.
Languages like Java turned that into Side effects, side effects and some more side effects.
Look at Rust and Go, their OOP implementation is based on value types and members-functions instead of classes, objects,methods.
This allows for writing completely side-effects free methods, as a method can be written as a function, that takes a copy of the value its invoked on.