And the backwards compatibility. One of the codebases I work on has loads of untouched 15 year old code that runs fine on Java 16. Good luck doing that in JS, Python, or really any other popular language besides C/C++
And the backwards compatibility. One of the codebases I work on has loads of untouched 15 year old code that runs fine on Java 16. Good luck doing that in JS, Python, or really any other popular language besides C/C++
far far more so, leaping to javas defense doesn't feel related to what this thread has been about. the thread has been about strategy & tactics, about escaping with something if the legal situation did go bad.
and as I stated, it doesn't seem like Google's Fuchsia does support Java. it might have been an idle notion, a legacy Android compatibility layer, but Java does not seem to be part of the modern Fuchsia attempt. at all. from what I can find. whatever pluses Java has, it doesn't seem like it's relevant enough to warrant any modern Fuchsia support. and the legacy Android support seems dubious / maybe non existent.
again I think the "fuchsia was just an escape hatch if Google had to have a non java based os" folks are a bit whack. but it was also a legit thread. even post Oracle trial, a break from 15 years of legacy & an underlying >2x as old posix api, for a more security conscious premise, sounds great, long long overdue.
Java has upsides but I don't think this thread should have to suffer that radical change in discussion. it muddies what was being talked about.
Fuscia and Java are both Android and tech related, don't see the problem. And the previous comment about Fuscia is just as off topic as mine, if not moreso. Java is at the core of Android and Fuscia hasn't made it out of the lab