If that were the case I'd just fix your comment instead of appending another comment after the fact. But that would make the arguments harder to reason about I think.
> including our code
Do you use git? Or does your team all just edit the same code on a shared server? (The OO solution here is to make state 'private'. It supposedly doesn't really matter than you're all editing the same documents at the same time, because they're behind getters and setters)
> why does the FP crowd make state even more difficult to reason about?
State is difficult to reason about so we maximise out stateless code.
> talking down OOP
I talk down OOP when I treat it as the diff between OOP and FP. That is, coding is 80+% the same whatever you use. It's the last 10-20% where the differences emerge: Lambdas are better than anonymous inner classes. Not having null is better than having null. Not needing to cast is better than casting. Composition is better than inheritance. Stateless is better than stateful. Value-equality is better than reference-equality. Generics + type erasure is clunky without higher-kinded types.