You can also write bad procedural code in an "OO language" because that is also a methodology. I see that crap all the time; giant 50+ line methods that do a bunch of things and all the utility functions are procedural-style class methods. Lots of Rubyists don't have any idea even what the difference between OOP and Procedural is, they just assume they must be doing OOP since they're using an "OO language."
... and in some cases breaking with OO methodology is the correct approach at least for Java. I'm thinking of squeezing performance out of an Android app on low end devices where it's a good idea to use the "static" keyword all over the place and in doing so treat member variables as globals and functions as effectively global subroutines. I think of it as risotto code - a big bowl of starchy mess that's a bit less stringy in appearance than spaghetti and potentially harder to get your head around.
Which sort of brings me to my view on whether or not Java is cool. Java itself is kind of like a swiss army knife that can be used to do just about anything you could want to do. It comes with a huge amount of bloat to that allows it to handle just about anything and while it's almost never as good as a specialist tool but you can always make it work. Swiss army knives are cool to boys between about 8 - 16 years old give or take. An adult with a swiss army knife in a leather pouch on their belt on the other hand is never cool.
Useful maybe, but never cool.