Web-standards-allergic Apple unveils WebGPU, a web graphics standard Apple, which once dismissed cross-platform development for forcing developers to use lowest-common-denominator technology, has proposed a cross-platform JavaScript API for 3D graphics rendered in browsers called WebGPU. The company's WebKit team, which steers the open source browser layout engine that Apple requires in iOS- …
A CAPTCHA's purpose is to not be able to be passed by an automated test.
So, no. Even if they beat today's, they won't beat tomorrow's.
If they're an inconvenience for you, tell the people who own the website / service that uses them. I guarantee they'll do nothing.
And just throwing power at a neural net does not make it any better at recognising images or any other tasks. That's why those kinds of tests are used in CAPTCHAs.
And we've had accelerated graphics - and by extension OpenCL etc. - for decades. It hasn't defeated CAPTCHAs, and neither will a proprietary Apple-only standard which does the same thing.
Automatically defeating CAPTCHAs would be... good, in your world? Are you even aware of the purpose of CAPTCHAs, or do you think web site administrators just like to annoy people?
I'd guess he doesn't. But to spell it out... Yes, captchas are annoying, but not as annoying as having to manage a website that can easily receive thousands of form submissions per hour all generated by bots (distributed bots, so often not from a single system or originating IP). In the middle of these thousands of form submissions are usually a few genuine ones, which have to be identified and dealt with appropriately. These thousands of bot generated submissions also rapidly fill a site's database. For just these two reasons it's well worth the marginal annoyance to reduce the number of bot generated submissions. As for how annoying a Captcha is for the genuine human, that's up to the site administrator and designer.
"Wasn't Apple actively using Metal a year or two before Vulkan was finalised?"
True, and that also applies to Microsoft, who've been using Direct3D in various incarnations for 20 years.
But, as in a lot of things, the time sometimes comes when it's better to go for interoperability than to try and force users/developers into your "ideal" way of doing things.
"The success of the web platform requires defining a common standard that allows for multiple implementations, but here we have several graphics APIs that have nuanced architectural differences,"
You and many others, but apple have a habit of doing their own thing.
They'll propose a standard the same time as implementing it in safari and push it out with the next iOS/macOS update. The W3C will than have little option but to adopt it because there will be a huge install base already. This has happened before.
The Register 
Biting the hand that feeds IT
Copyright. All rights reserved © 1998–2024
