this post was submitted on 01 Oct 2023
-14 points (40.5% liked)

Technology

59347 readers
5295 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots


founded 1 year ago
MODERATORS
 
  • extended update service to 7 years
  • pushing Material UI consistency
  • Tensor G3 chip for AI & machine learning performed locally on device
you are viewing a single comment's thread
view the rest of the comments
[–] kirklennon@kbin.social 28 points 1 year ago (2 children)

Like seriously, what’s the percentage of people that run machine learning algorithms on their phone? 0.0000000001%?

It’s 100%. You use them on your phone all day every day. Your keyboard used machine learning algorithms as you typed your comment to dynamically adjust the size of the tap target of your likely next character and for autocorrect.

Every single photo taken on a phone is run through a huge amount of ML to create it.

All of this is to say, however, that this headline is ridiculous. Aside from Material UI, this is basically a description of every iPhone from the last half decade (with a dedicated “neural engine”). Not really a change in the smartphone world.

[–] Salamendacious@lemmy.world 5 points 1 year ago

Definitely a little bit of hyperbole with that headline. I think I have to use the exact headline the article uses though.

[–] rush@lemm.ee 4 points 1 year ago (1 children)

I agree in the fact that some ML algorithms are used daily by nearly all who have a smartphone, but things like increasing the touch target is BS. It's quite easy to confirm by simply either looking at the code or enabling "show layout bounds" in Android's Developer Options.