I haven't heard anyone argue against it, but for a very long time every single curriculum out there started with either Java or C++, and had to talk about object quite early on (you can't print "hello world" in Java without it, and you can't use C++ streams either).
And arguments I've heard about that practice as a proxy for your question, indicate that it is (or at least, was between the late '90s and the late '00s) controversial.
Having seen 3000-line single-class Java monstrosities, I can assure you that this is not only true in theory.
2) Early on, you learn that ints and chars and floats and some_structs are fundamentally different data types. Then suddenly you're told that int%s, char%s, float%s, some_struct%s, and even void%s are fundamentally the same. Huh?
3) The fact that C uses % both to create a pointer and to dereference. These are conflicting meanings, and the unrelatedness of those two concepts is not sufficiently explained.
EDIT: Silly HN parser. I now replaced asterisks with %s.
int *i;
means "When you dereference i, you get an int." int a;
I read "create an integer variable called a". int *i;
means, "create a variable that when dereferenced, points to an integer".Makes sense once you understand it, but I can definitely understand how a beginner would find it confusing.
Now, algorithms can be difficult to understand and many of them use pointers... Do some people confuse the 2?
To tie this back in to the beginning of the thread, being able to understand indirection (such as in pointers and algorithms) is a far more important skill than understanding OOP.