Google IO: A deeper dive into the developer day's details Google's developer keynote at its IO show on Wednesday focused on Android and on web technology, which suddenly looks much more capable thanks to WebGPU, an API that allows web applications to tap into local GPU hardware. Chrome 113 arrived with WebGPU switched on by default in early April, and Google is pitching the …
What we're edging our way towards is a universal desktop API that can support both local and remote back-end applications.
Given the route by which we arrived here, what's particularly interesting is that with a bit more work on a portable language runtime (and it's arguable WASM is insufficiently ambitious) we could finally ditch HTML and JavaScript and use development languages of choice in both clients and servers. I never cease to be amazed at the propensity of IT to return to its point of origin, regardless of how far it periodically meanders away.
So Android Studio has gained an AI has it.
If that AI has any 'intelligence' it will, from the first instance it looks any anything in Android Studio, demand the entire monstrosity be binned.
I can only guess polishing a turd is the next big thing these days.
Did they have a meeting where they specifically discussed how they could make it much easier for cryptominers and other machine hijackers to misuse other people's computers? Or has nobody yet clicked that allowing arbitrary low level web assembly code downloaded automatically from a webpage to access hardware is a really really bad idea?
The Register 
Biting the hand that feeds IT
Copyright. All rights reserved © 1998–2023
