3 ms·
I think the answer lies in the late '80s computing zeitgeist. During the preceding decades, the object-oriented paradigm had been shown to be highly useful in
by pavlov 12y ago
I think the answer lies in the late '80s computing zeitgeist.
During the preceding decades, the object-oriented paradigm had been shown to be highly useful in simulation (Simula) and graphical UIs (Smalltalk), but these use cases were still far removed from the majority of real-world apps.
A lot of people looked at OO's phenomenal success in these fields and extrapolated that all software would soon look like that. "GUIs are going to be the future. Also, all of our software works with real-world stuff. Money exists in the real world, right? Therefore it's an object."
Java certainly didn't start the OO hype. By the time Java hit, the hype had already been in full force for at least 5 years... Borland's CEO announced sometime around 1992 that they would defeat Microsoft by adopting a "full OO" development workflow. At the same time, Microsoft was hyping its own OO concepts and frameworks like MFC.
But Java definitely hit the sweet spot of multiple hype cycles at once with its combination of OO everywhere, web-oriented applet deployment and platform-independent VM.