Right, but that's just another architecture to support for testing, which can (hopefully) be largely automated. I'm not saying that there won't be growing pains, just that they will be more along the lines of testing an app locally vs testing an app in a docker container in a kubernetes cluster. Same app, but different results due to different Java runtimes, firewall rules, etc...Our systems run on x86 so our apps need to be compiled and tested on x86 versions. Saying "Well it worked on the ARM versions" isn't going to fly in that type of environment.
so macs are becoming solely consumer products.
Good bye to professional/specialised software.
I think its long overdue.
Via are an x86 licensee so most likely it was a Via x86 CPU. Transmeta did have a CPU that sort of worked like that. Was not very fast thoughcould always stuff in x86 emulation compatability layer
i had some kind of Fujitsu laptop 20 years ago with a Via CPU that did that. It was fine.
I think its long overdue.
Apple's notebooks have had flawed airflow + cooling designs for years causing the processor to constantly overheat and run at slower speeds. I don't want to hear excuses about Intel's bad performance before they haven't at least tried to get the best performance out of their hardware.I think this is much more of a “they’re FINALLY ditching Intel” situation
Stupid question - will these MacBooks be able to bootcamp Windows, or to run software like Citrix to remote login to Windows machines?
Does this mean I should avoid buying a 2019 MacBook Pro (upgrading from a 2012) just yet?
I need x86 to do my job. This could eventually end my use of OS X, at least for work, which would really suck. I've been using OS X since literally day one in March 2001.
But if Apple is going to peel off a substantive subset of the entire lineup for their own A-Series derivatives, the question is really whether AMD can cover what is left. As long as it was a super broad, diverse set of CPU products then Intel had leverage.
AMD has gotten off the extremely dubious tactic of trying to go "blow for blow" across the entire Intel CPU product space. If the subset that AMD picks is the area that Apple doesn't want to do then will make them much more viable as a component supplier in that "new boundaries" space.
There is no question AMD could screw things up. For the last couple of years though they are on executing at least as good as Apple is in its subset market targets. Apple just dropped a A12Z to limp along until can get A14X out the door. The gap between A10X and 12X isn't going to much better for 12X to 14X.
AMD has done 14nm -> 12nm -> 7nm on pretty smooth sequence on desktop processors. Looks like Zen3 is a sensible, limited optimization of a narrow set of "could be better" issues at 7nm and will start rolling out at end of 2020. AMD doesn't need a magical technological lead, they need to execute. ( because Intel isn't. )
What kind of GPUs are these things going to have? Obviously not Intel graphics. Can you even put an AMD GPU with an ARM processor? I know Nvidia can with the Tegra series and such.
This is going to be the death of the Mac computers as a whole. Arm Macs won’t have any compatability with any of the software available until the software developers update their software and most will be left behind. Microsoft tried to transition to ARM with the Surface Pro X and Windows 10 on ARM has been a failure. I expect this to fail as well, especially since ARM will probably not have the same performance for all tasks compared to X86-64.
I have always been a Mac guy, but my current Pro is probably the last one I will own. You just get so much more bang for your buck with PCs, and have so many more options. There is nothing specific that I do that I cannot accomplish with a PC.
You are not a software developer, are you? And specifically you are not a MacOS developer? Unless you write assembler code, and only have assembler code for Intel processors (I use some libraries which have assembler code for Intel and ARM), you just switch the compiler to "ARM", build it, put it on the App Store - that's it.This is going to be the death of the Mac computers as a whole. Arm Macs won’t have any compatability with any of the software available until the software developers update their software and most will be left behind. Microsoft tried to transition to ARM with the Surface Pro X and Windows 10 on ARM has been a failure. I expect this to fail as well, especially since ARM will probably not have the same performance for all tasks compared to X86-64.
How does that relate to the article?
You are not a software developer, are you? And specifically you are not a MacOS developer? Unless you write assembler code, and only have assembler code for Intel processors (I use some libraries which have assembler code for Intel and ARM), you just switch the compiler to "ARM", build it, put it on the App Store - that's it.
I am a professional software developer, probably been one before most posters here were born, and I ran some benchmarks on an iPhone XR vs. quad core iMac. The iPhone absolutely killed the iMac. With just two fast processors (plus four energy saving ones) vs. four processors. So that's your "probably not" against my "I ran the tests".
Developer here: No. You open Xcode with your project, click on the project file, then under "Build Settings" you click on "Archs" and add aarch64 to the list of architecture (that's 64 bit ARM). Then you press "Build" and you're done.wouldn’t this be a nightmare for developers?
I am a software developer and I do develop open source software for both macOS and iOS/iPadOS. I know about this since I managed to port my iOS app using Catalyst to see how it performed, but decided not to release it. This is nothing new, but I am still against the idea of ARM Macs mostly for compatability reasons with really little benefit for running apps from iOS. I own a iPad Pro with a magic keyboard can already do that without alienating the pro users by switching everything to ARM.You are not a software developer, are you? And specifically you are not a MacOS developer? Unless you write assembler code, and only have assembler code for Intel processors (I use some libraries which have assembler code for Intel and ARM), you just switch the compiler to "ARM", build it, put it on the App Store - that's it.
I am a professional software developer, probably been one before most posters here were born, and I ran some benchmarks on an iPhone XR vs. quad core iMac. The iPhone absolutely killed the iMac. With just two fast processors (plus four energy saving ones) vs. four processors. So that's your "probably not" against my "I ran the tests".
Now try a game with both, but has to run with UHD graphics and high FPS. The iPhone will not even run it. *evil laugh*.
My benchmark is games like F1 2019 and first person high quality shooter games. If it can run these games with top quality, then you have a winner. but ARM will never do it.
What I don't understand in some of these articles discussing this ARM Mac is references to datacentres already running ARM. Which ones? Everything that I've come across is still using x86/x64 (AWS, Google Cloud, Rackspace and SAP to name but a few that I work with every day)
and to transition thousands upon thousands of servers to ARM is a gigantic undertaking.
Having an ARM-based Mac whilst operating in server environments which are going to be x86/x64 for a very long time coming is going to be a massive pain. Fine for consumers, but for developers and sysadmins - many of whom use Macs, not so much.