Stories
Slash Boxes
Comments

SoylentNews is people

posted by Fnord666 on Tuesday June 23 2020, @07:56AM   Printer-friendly

Apple announces Mac architecture transition from Intel to its own ARM chips, offers emulation story

Apple has just announced its plans to switch from Intel CPUs in Macs to silicon of its own design, based on the ARM architecture. This means that Apple is now designing its own chips for iOS devices and its Mac desktop and laptops. Apple said it will ship its first ARM Mac before the end of the year, and complete the Intel -> ARM transition within two years.

Apple will bring industry leading performance and performance-by-watt with its custom silicon. Apple's chips will combine custom CPU, GPU, SSD controller and many other components. The Apple silicon will include the Neural Engine for machine learning applications.

[...] "Most apps will just work".

The Next Phase: Apple Lays Out Plans To Transition Macs from x86 to Apple SoCs

[From] an architecture standpoint, the timing of the transition is a bit of an odd one. As noted by our own Arm guru, Andrei Frumusanu, Arm is on the precipice of announcing the Arm v9 ISA, which will bring several notable additions to the ISA such as Scalable Vector Extension 2 (SVE2). So either Arm is about to announce v9, and Apple's A14 SoCs will be among the first to implement the new ISA, otherwise Apple will be setting the baseline for macOS-on-Arm as v8.2 and its NEON extensions fairly late into the ISA's lifecycle. This will be something worth keeping an eye on.

[...] [In] order to bridge the gap between Apple's current software ecosystem and where they want to be in a couple of years, Apple will once again be investing in a significant software compatibility layer in order to run current x86 applications on future Arm Macs. To be sure, Apple wants developers to recompile their applications to be native – and they are investing even more into the Xcode infrastructure to do just that – but some degree of x86 compatibility is still a necessity for now.

The cornerstone of this is the return of Rosetta, the PowerPC-to-x86 binary translation layer that Apple first used for the transition to x86 almost 15 years ago. Rosetta 2, as it's called, is designed to do the same thing for x86-to-Arm, translating x86 macOS binaries so that they can run on Arm Macs. Rosetta 2's principle mode of operation will be to translate binaries at install time.

See also: Apple Announces iOS 14 and iPadOS 14: An Overview
Apple's First ARM-Based (Mac) Product Is a Mac mini Featuring an A12Z Bionic, but Sadly, Regular Customers Can't Buy It

Previously: Apple Will Reportedly Sell a New Mac Laptop With its Own Chips Next Year


Original Submission

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 2) by toddestan on Wednesday June 24 2020, @12:39AM (3 children)

    by toddestan (4982) on Wednesday June 24 2020, @12:39AM (#1011775)

    I've also suspected that's their ultimate goal - to turn the Mac into the same kind of walled garden that the iPhone/iPad is. Getting a sweet 30% cut of every software sale on the Mac must be mighty tempting.

    Anyone who wants or needs a computer will still buy a computer - it just won't be one with a fruit on it. Not that Apple has made a serious computer for some time now - the Mac Pro has been a joke for years now.

    Starting Score:    1  point
    Karma-Bonus Modifier   +1  

    Total Score:   2  
  • (Score: 2) by Pino P on Sunday June 28 2020, @06:04PM (2 children)

    by Pino P (4721) on Sunday June 28 2020, @06:04PM (#1013750) Journal

    Anyone who wants or needs a computer will still buy a computer - it just won't be one with a fruit on it.

    Unless you develop software for a living or as a hobby. No fruit, no access to the market of Mac, iPhone, and iPad users. Even if you plan to deploy your application as a web application, you still needed a Mac in order to debug the client side in Safari last I checked.

    • (Score: 2) by toddestan on Monday June 29 2020, @01:49AM (1 child)

      by toddestan (4982) on Monday June 29 2020, @01:49AM (#1013933)

      The Mac software market has been shrinking for some time now, and some of the big developers on Mac such as Adobe have switched from developing on the Mac and porting to Windows later to developing on Windows and releasing a Mac port later. It's a pretty good bet a lot of them are going to give some thought as to whether it's worth going through another transition.

      As you allude to, the big market for Macs is to develop software for iOS, and will continue that way so long as Apple doesn't open up their platform (and iOS remains relevant). This could take a pretty big hit if Apple starts allowing for development to take place on iPads, as you could always just use an iPad + keyboard instead of Mac. Assuming that iPad + keyboard isn't just a Macbook anyway.

      While I'm sure anyone developing websites cares about Safari on iOS, I kind of doubt it for Safari on the Mac. Sure, some will care, but I would guess a lot would test on iOS Safari and assume Mac Safari will work too for the small fraction of Mac users who actually use Safari. And if it doesn't, the answer will just be "install Chrome" anyway.

      • (Score: 2) by Pino P on Sunday July 05 2020, @02:10AM

        by Pino P (4721) on Sunday July 05 2020, @02:10AM (#1016348) Journal

        While I'm sure anyone developing websites cares about Safari on iOS, I kind of doubt it for Safari on the Mac.

        The debugger and inspector tools for Safari on iOS are displayed inside Safari on macOS.

        And if it doesn't, the answer will just be "install Chrome" anyway.

        Chrome for iOS uses the same WKWebView control as Safari for iOS and thus has the same engine quirks.