> In this situation, a significant new revenue stream ( an Android tax) is definitely worth fighting for.
Except that there is no hope of that ever happening. Even if Oracle won in a big way, then Google would eat the one-time cost of deprecating the Java API on Android, similar to what Apple did between Objective C and Swift. There is no sustainable revenue stream there.
They have already done that, in practice - Google keeps coming up with other ways of writing Android apps and alternative runtimes, and encouraging developers to adopt them. It would have been silly not to, the minute Oracle sued, as insurance. But it’s a mammoth task and nowhere near completion. Moving such a humongous ecosystem is always hard; if you cut too abruptly you risk opening the market to competing platforms. This goes even more for a platform that has customers both above (developers) and below (manufacturers) the stack. Apple didn’t even change anything of substance internally, and still a lot of (most?) apps are not built with Swift. It will take years to replace Dalvik; and in those years, the crocodile would be happy to collect.
You can't do it overnight, but you can do it over an abbreviated time frame. Especially once you're sure you need to.
Then it could be announced that the Java API will be removed in a specific future version (so update your applications now), the Google Play cut of applications using it will now be 50% instead of 30% for those without it, some of the OEMs will immediately start selling phones that don't have it and those phones are less expensive so people will buy them and developers will have to use the new replacement to reach those app customers, etc.
Forcing a transition to happen faster is not fun, but that isn't the same as not possible.
Still the same stdlib API, at least the way Google has introduced Kotlin to Android. If they had any ambition to use Kotlin as their vehicle for abandoning the Java API I would expect at least some visible efforts of opening Flutter to languages other than Dart. But in typical Google fashion they seem to deliberately avoid forcing their teams down in the trenches into some unified grand strategy, giving them the freedom to build the best version of their product that they can. Given Google's deep pockets and how badly coordination overhead would scale to their project dimensions, this hands-off approach seems reasonable enough.
Except that there is no hope of that ever happening. Even if Oracle won in a big way, then Google would eat the one-time cost of deprecating the Java API on Android, similar to what Apple did between Objective C and Swift. There is no sustainable revenue stream there.