How Apple Built a Chip Powerhouse to Threaten Qualcomm and Intel

Re:How Apple Built a Chip Powerhouse to Threaten Qualcomm an... by pjmlp on Tuesday January 30, 2018 @02:38PM (#16268272)

It is, in the age of ubiquitous multi-core hardware.

I don't remember when it was the last time any of my applications only had a single thread of execution on them, beyond shell and Python scripts.

Maybe around 2000.

And even then, the OS is juggling processes across all cores every few ms, so outside any benchmark winning game, there isn't much real world value in single thread performance.

[ Parent | on HN ]

Re:How Apple Built a Chip Powerhouse to Threaten Qualcomm an... by eecc on Wednesday January 31, 2018 @04:49AM (#16272713)

Are you serious? Multithreadjng is not Parallelism. It’s not about processing an image in the UI thread, it’s about making that processing faster on the background thread that picks up the work. Don’t get me wrong but lots of people still write iterators, for loops and single threaded functions. Parallel algorithms are hard

[ Parent | on HN ]

Re:How Apple Built a Chip Powerhouse to Threaten Qualcomm an... by jasonvorhe on Tuesday January 30, 2018 @02:51PM (#16268373)

Except for JavaScript performance: https://twitter.com/codinghorror/status/954493740600578049

[ Parent | on HN ]

Re:How Apple Built a Chip Powerhouse to Threaten Qualcomm an... by pjmlp on Tuesday January 30, 2018 @03:57PM (#16268953)

What I see is the quality of a JIT compiler implementation, not the use of cores.

[ Parent | on HN ]