What you need to know
- Craig Federighi, Greg Joswiak, and Johny Srouji sat down for an interview about Apple silicon.
- The conversation covered its origin and the reasons why and why now.
As part of the company's campaign trail to talk about the new M1 processor, Craig Federighi, Apple's Senior Vice President of Software Engineering, Greg Joswiak, Apple's Senior Vice President of Worldwide Marketing, and Johny Srouji, Apple's Senior Vice President of Hardware Technologies all sat down virtually with Ars Technica for an interview.
When asked why Apple was switching to its own silicon for the Mac, and why now was the right time, Federighi talked about how important the Mac has always been to the company and the people who use it.
While some thought that Apple's transition to Apple silicon may have been a result of Intel's lackluster performance in recent history, Greg Joswiak says that the M1 chip and its future family was more of an internal ambition.
Srouji says that he and Federighi actually work very closely together from the inception of something like the M1 chip.
The interview is wide-ranging, covering the new unified-memory architecture and how Apple sees iPhone and iPad apps coming to the Mac. You can read the full interview at Ars Technica.
Joe Wituschek is a Contributor at iMore. With over ten years in the technology industry, one of them being at Apple, Joe now covers the company for the website. In addition to covering breaking news, Joe also writes editorials and reviews for a range of products. He fell in love with Apple products when he got an iPod nano for Christmas almost twenty years ago. Despite being considered a "heavy" user, he has always preferred the consumer-focused products like the MacBook Air, iPad mini, and iPhone 13 mini. He will fight to the death to keep a mini iPhone in the lineup. In his free time, Joe enjoys video games, movies, photography, running, and basically everything outdoors.
Thank you for signing up to iMore. You will receive a verification email shortly.
There was a problem. Please refresh the page and try again.