Technology

59578 readers

3092 users here now

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

Our Rules

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

Approved Bots

founded 1 year ago

MODERATORS

305

Intel doesn’t think that Arm CPUs will make a dent in the laptop market (arstechnica.com)

submitted 1 year ago by L4s@lemmy.world to c/technology@lemmy.world

130 comments fedilink hide all child comments

Intel doesn’t think that Arm CPUs will make a dent in the laptop market::"They've been relegated to pretty insignificant roles in the PC business."

you are viewing a single comment's thread
view the rest of the comments

[–] just_another_person@lemmy.world -3 points 1 year ago

Quick responses, sorry.

gaming is a problem for people who DO want this type of machine, and not a second or console. It's only become an issue with M*
Apple has literally thrown an entire engineering group behind their ability to import, export, and transcode media. So much so they even have their own fork of ffmpeg. It's atrocious.
PyTorch is CPU with GPU acceleration where applicable, and most devs want direct GPU access. Not possible on Apple hardware. LLMs are kinda dumb, and most people work on imaging inference. Direct access to the hardware for local development is a must.
Not sure what you mean, but Rosetta is essentially QEMU emulation, which is insanely slow. I can run a 2m build for something on a native x64 machine, or a 1 hour build through Rosetta. No thanks.
This is a power play by Apple thinking people will still buy their stuff and just deal with the inconveniences, but turns out the sales numbers show that is not the case.

In general, the "use containers for everything" is not a good workflow. It's also very subjective to performance on the platform you run it on. Containers all the time is exhausting and problematic for a number of different reasons.