Like, seriously? Prototype-based programming isn't even real inheritance </controversial>
Most opponents to prototyping seem to be because it's unfamiliar and/or because they don't like/understand JavaScript. (And if it wasn't for JS most people would remain ignorant of the existence of it.)
Of course, if you're working in a decent language, you're not limited to one way or another, and can roll with either classes or prototypes depending on what is most appropriate for the task at hand.
(And if you're working with JavaScript... there's still class-based implementations for it.)
With regards static typing, lots of people like it because it lets them be stupid and gives a [false] sense of security when the compiler succeeds.
The same sort of people will use a 15-20 line namespaced XML file (accompanied by an even longer XSD schema) instead of just using a 1-2 line INI file.