Part of the answer is that Java still advance the state of the art for most people: It got safety and garbage collection accepted by the mainstream.
Oberon etc were not in reach for the average Joe, the tooling was too expensive and the cheap, resource constrained PCs couldn't run it. The language required sophistication from the programmers. Nobody was available to answer questions, the ecosystem wasn't there.
Java, o.t.o.h. had something for everybody. It was safer than C, important if you wanted a stable web server. It was faster than perl or shell scripting, so you also had a cheap web server. The browser got nicer graphics from applets. Enterprise architecture got a way forward from CORBA to JEE without having to admit something was wrong. Hardware vendors got a way to stay relevant in the face of Windows. Tooling vendors and consulting companies got a reason to sell. Managers got cogweel replaceable programmers. Schools got a reasonable and vendor-neutral language. Even if none of promises was completely fulfilled, it was close enough long enough.
So basically the language design resources for Oberon were in the end more wasted than those on Java. 'Worse is better' once again.
I'm sorry, but that's just nonsense. You can argue lack of documentation and user community, but Oberon is about as resource economic as it gets, and was originally designed for mid-80s hardware.
* It wasnt very visible in the ICT media. Sun did a full steam ahead Java Campaign
* Open source at the time was not seen as trustworthy. I did run Linux at the time. SO did you, probably. Corporations would not touch it with a 10 feet pole. I presume oberon was seen in the same light.
If Java was sold for the same price as lets say Delphi, most devs and university students would never have cared.
Take Java for example.
When it came into scene we had Oberon and its variants, Ada, Modula-3 and Eiffel.
All supported JIT/AOT compilation, value types, and with exception of Oberon, generics.
Most of the last changes at the JVM level, and the upcoming ones on Java's roadmap are basically catching up with what was already possible in the mid-90's.
So how much money could Sun, Oracle and IBM have saved if those features were there from the beginning?
We will never know, but we will know how much the bill is going to be, given that it is 10+ year process currently.
All because the current hardware changes make it impossible for Java to continue to ignore those features, if it is to stay relevant against other languages.
Same applies to other languages in different ways.