Performance of LINQ Any vs FirstOrDefault != null

Question

There are multiple places in an Open Source Project (OSP) code I contribute, where it has to be determined if an element in a collection satisfies a certain condition.

Answer 1

Why should any continue after it has found an element satisfying the condition? If the condition applies to 1 element, that qualifies as "any".

I think they should both perform about the same, but Any() does express your intention more clearly.