AppleInsider podcast talks 'iPhone 8,' Mac Pro, Thunderbolt GPUs & more

Comments

• Reply 1 of 7

  falconaire Posts: 6member

  April 21, 2017 5:30PM

  And in other news with MS coming out with an ARM based Win10 system based on Qualcomm's Snapdragon 835 can we possibly see Apple move towards an macOS system based on ARM as well so that the A processors can be even better used and Intel doesn't have to be relied upon to update their processors every 5 years for Apple products? Just my hope and thoughts for future products. Maybe the Mac Pro can be Intel and the consumer iMac's use the ARM chips since if we can still run Win10 full apps (which is what some of us have to do at work since programmers haven't converted everything to Swift yet. ).

  
• Reply 2 of 7

  appex Posts: 687member

  April 21, 2017 7:11PM

  Mac compatibility with Intel x86 (read, NO ARM) is a must.

  
• Reply 3 of 7

  k2kw Posts: 2,075member

  April 22, 2017 2:39AM

  Niel, thanks for correcting DED on Android Auto.    If DED feels that Android Auto is so bad on a variety of current/recent android phones AppleInsider should do a video where he compares the APPLE 7 & SE phone against two Android flagships and two mid range phones in atleast 3-5 different cars.   Would be a great project to see this tested.  

  
  

• Reply 4 of 7

  DanielEran Posts: 290editor

  April 23, 2017 4:06AM

  k2kw said:

  Niel, thanks for correcting DED on Android Auto.    If DED feels that Android Auto is so bad on a variety of current/recent android phones AppleInsider should do a video where he compares the APPLE 7 & SE phone against two Android flagships and two mid range phones in atleast 3-5 different cars.   Would be a great project to see this tested.  

  
  

  According to Android Central, which wrote up "what works with Android Auto" last summer, " If there's a weak link for Android Auto, it comes when you actually plug the phone in. Because the various Android manufacturers do all sorts of nonsense to their phones, including what happens when you plug one in. And on occasion, Android Auto might not work at all."
  
  Specific to Samsung, the article noted:
  
   "Samsung sells more Android phones than anyone. They're also more customized than just about anything out there. There's good and bad news here. Take the Galaxy S7, for example. There are folks who have used it without issue. And then there are those of us who have never gotten the GS7 to work. Maybe it's a software issue. Maybe there's something inherent about the GS7 that doesn't like the cable I'm using. I don't know.
  
  "But I do know that there are 31 separate versions of the Galaxy S7 (worldwide). Some work. And some don't. Again, I'll point you to the forums."
  
  http://www.androidcentral.com/best-phone-use-android-auto

  edited April 2017
• Reply 5 of 7

  Mike Wuerthele Posts: 6,861administrator

  April 23, 2017 12:24PM

  k2kw said:

  Niel, thanks for correcting DED on Android Auto.    If DED feels that Android Auto is so bad on a variety of current/recent android phones AppleInsider should do a video where he compares the APPLE 7 & SE phone against two Android flagships and two mid range phones in atleast 3-5 different cars.   Would be a great project to see this tested.  

  
  

  While I'm curious about this too, I'm not certain what magnitude of resources you think we have at our disposal

  edited April 2017
• Reply 6 of 7

  misa Posts: 827member

  April 23, 2017 8:47PM

  falconaire said:

  And in other news with MS coming out with an ARM based Win10 system based on Qualcomm's Snapdragon 835 can we possibly see Apple move towards an macOS system based on ARM as well so that the A processors can be even better used and Intel doesn't have to be relied upon to update their processors every 5 years for Apple products? Just my hope and thoughts for future products. Maybe the Mac Pro can be Intel and the consumer iMac's use the ARM chips since if we can still run Win10 full apps (which is what some of us have to do at work since programmers haven't converted everything to Swift yet. ).

  Ha no. It needs repeating many many times, you are not going to see anything with an ARM CPU running Windows or MacOS that isn't inherently awful.
  
  The ARM chips that Apple use are not comparable to a desktop, not by a long shot. The closest is roughly performance parity with a 6 generation old mid-tier laptop intel CPU. 
  
  You may see ARM chips in tablet-like devices or tablet-convertable devices but you're not going to see Apple or Microsoft just up and go "Intel party train is done, time to ARM", Apple is not in the predicament it was in when it switched from PPC (which video game consoles all switched FROM this generation) where nobody was actually producing any parts for them.
  
  Apple would not be able to build enough ARM parts for both their iPhone/iPad lines and any other computer systems. It just is not going to happen. The iPad Pro and the Apple Macbook Air notebook slot into exactly the same user business case, but the iPad Pro probably works out to be better for full time use, where as the Macbook Air probably works out to be completely useless if it switched to ARM.
  
  That is what you're going to see. Nobody seemed to take the lessons from Android seriously. People build software in C/C++, not some platform-proprietary language in order to run on all CPU types. Java has been a colossal fail for the desktop, and needs to die in phones too. Nobody loves Android development because it's a rubbish platform to begin with, worse than the Win3.0/3.1/95/98/ME evolution where at least Microsoft finally threw out the bathwater in Windows NT 4.0/2K/XP and it stopped sucking to build windows software because it no longer had to work on 9x.
  
  
• Reply 7 of 7

  vmarks Posts: 762editor

  April 23, 2017 11:43PM

  k2kw said:

  Niel, thanks for correcting DED on Android Auto.    If DED feels that Android Auto is so bad on a variety of current/recent android phones AppleInsider should do a video where he compares the APPLE 7 & SE phone against two Android flagships and two mid range phones in atleast 3-5 different cars.   Would be a great project to see this tested.  

  
  

  We could test a budget and flagship phone on two aftermarket systems, the pioneer nex4100 and kenwood ddx9902. We have an Honor 6x, Alcatel Pop 4 Plus, and a Nexus 6P at our disposal. The forums that DED points to are correct that some have slight difficulty when connecting to the radio (although this doesn't appear to be true as of the updates last fall), but that's not the defnition of 'running android auto.' AA runs on the phone and displays the same display as it would on the car radio on the built-in screen. It runs on android phones from 5.1.1 to 7.x. Yes, Samsung has a bunch of phone models that use the SGS7 name (US sku, EU sku, KR sku, etc.) but I still can't think of a flagship phone that can't run Android Auto. A better example might have been Google Assistant, which is reserved for Pixel, even though it's been promised to run on select Nougat phones at some point in the future, and has been proven to be possible to run on Marshmallow and Nougat. Google is trying to ease the OS updates problem, while at the same time moving things that need to be updated (Android Auto, Maps, Launcher, Messages, etc) into Play Store, where they have a direct path to the consumer, and the carrier and handset mfr can't get in the way.
  

  edited April 2017