On top of that Java has the brand.

Programmers may not feel positive about it but it's embedded in a lot of large organisations, many of whom will, at the management level, be perfectly happy with the Oracle acquisition. They won't see the need or the appeal to move to something else until there is a strong incentive to do so.

Against that sort of entrenchment programmers will struggle to influence things a whole load in a lot of Java's key markets.

Users have little obligation with respect to the Java trademark. My organization can use the word "Java" internally to remind our execs that we're doing the safe, boring thing, and there's no problem if we actually deploy Lava or Fava or Cava (my pick) to our servers. As long as we don't publicly advertise that our services rely on Java technology (and who does that anymore?) we're free to call anything Java internally.

If Oracle targets an "OMG Don't Get Caught Using Fake Low-Quality Java" marketing campaign at our upper management, we'll talk to management ourselves and paint Oracle as losers who lost their grasp on everything but the trademark and no longer offer the premier, industry-standard implementation that we require.

Oracle doesn't do marketing like that.

Oracle doesn't care what you do, unless you are in their target market: enterprise software.

If you are, then no amount of talking to management will trump the potential of their talk with management: "Sorry, you are using an unsupported configuration. Your 500K support contract is now void, you will no longer receive critical updates and your licence will expire at the end of the month. Good luck getting your data out before then. Oh, BTW, if you keep your database running after the licence is expired then we'll sue you"

You'll never win taking Oracle on head on like that.

OTOH, they are very vulnerable to new applications that just happen to be written in Cava on a JVM-derived virtual machine.