The problem with OOP isn't objects or classes, but it is the oriented part. The thing is, there are quite a few applications that do not need to, and are not best designed to be, objected ORIENTED. Not everything is best represented by a class, and it tends to overcomplicate simple solutions at times. An example of this is when you just need to get a few quick things done but you end up having to new up like 5 objects on the heap just to do so. If you've done OOP for any length of time, especially when you had to use someone's library, I know you know exactly what I'm talking about:
var provider = RestaurantIngredientServiceProvider.Create();
Restaurant restaurant = new Restaurant(Location.Texas);
IngredientsList ingredientsList = new IngredientsList(provider);
MenuItem sandwich = new Sandwich(ingredientsList);
sandwich.Make();
That kind of thing can be cumbersome; and by the way this example is very contrived; what can I say, it's 2am. But if you really want to see what I mean by this, go check out some of the types on this page. Microsoft in particular seems to be good at throwing all kinds of ridiculous OOP crap around. IMO, this can be an ugly way to solve problems.
Another valid argument that I've heard about OOP is that, by definition it's a little strange - why are we orienting towards objects for? We should be orienting towards solving the problem and I agree wholeheartedly, which is why I prefer object-capable but not necessarily object-oriented approach. It's a feel thing for sure... Best way to get what I'm saying is to write an application using class-city in a language like C# or Java, then go do that in C. C's syntax may be a little more cryptic at first, but the solution is often a lot more elegant and simple. Not to mention, we say OOP has encapsulation, when in reality, it broke the encapsulation that C's header/source system had. Want encapsulation? Just leave the function in the source file and out of the header. Bam, perfect!
As aforementioned, I wouldn't necessarily say one paradigm is "better" than the other overall. Use the right tool for the job. Unfortunately, most people bandwagon to whatever the trend is regardless of the job.