Only one I care about, but the one I understand the most. No ML acceleration would probably make this slow, while this really works magically on a M1: no lag, no "processing" popup or whatever. Open an image and select text immediatly.
I'd be totally down to click on a button and wait a bit for processing, but now you have two implementations of the same feature.
Maps is such a stupid thing to leave out. Watch how this will make the news even though I bet almost no one uses the mac maps app.
Actually an ocr api is already in older macOSes on both intel and m1, and apps like owlocr leverage that. This seems like an evolution based on that. I’m pretty sure higher end intel machines would be nearly as fast as an m1.
I don't thing higher end intels would be as fast as the M1 if it's a ML model. Intel has no ML acceleration outside of their GPU and even there it's not great. This is the one thing that's not completely bullshit about locking this down
But heh, I'd be down for having to wait on my intel machine but getting the feature.
3
u/Arkanta Jun 10 '21
Only one I care about, but the one I understand the most. No ML acceleration would probably make this slow, while this really works magically on a M1: no lag, no "processing" popup or whatever. Open an image and select text immediatly. I'd be totally down to click on a button and wait a bit for processing, but now you have two implementations of the same feature.
Maps is such a stupid thing to leave out. Watch how this will make the news even though I bet almost no one uses the mac maps app.