We just think the time is right for a language that makes it easier to create components. The case of OOP Implementing features in a language stems from the same reasoning process which makes you write a function to wrap an often-recurring sequence of actions. Or more generally which makes people create new words for new concepts as soon as that concept is used often enough. OOP brings new concepts, so it's logical that the language should let you use them directly, instead of forcing you to do so through their underlying description. And a programmer is very unlikely to use a feature if it's not easy to get working.
Programmers are lazy by nature, programming is about being lazy.
It's about getting the machine to do as much of the job as possible. Because of this, a programmer is much less likely to create classes in a non-OO language with an OO framework added than in an OO language. Typically, he will end up having a relatively few number of very large classes. Also, such a framework tends not to be very scalable both up and downwards. To implement things like OO Design Patterns is quite hard.