godofbiscuits

spheric said:

Is this really relevant to the mainstream though? 

I’m not knocking the tech; I’m asking because I have not seen any use case example so far that is at all relevant to my personal experience. 

It’s nice to be able to see the new Mac Pro in VR sitting on the bathroom floor, but beyond that, the technology hasn’t enriched my life. 

Gaming I get, home improvement and 3D models, I get — but those really aren’t mass interests, are they? 

Have you seen how popular IKEA is? Have you been to one on a weekend? Potentially every time every person or family visits one is a session or sessions of using AR beforehand to help decide which piece of furniture to buy. The entire high tech industry has been built on “we don’t know all that folks will use this for yet”. The Apple Watch wasn’t initially introduced as a health device. Right now it requires an iPad or iPhone to use as a “universe window” (props to the tv show ”Fringe”), but a whole new set of uses become available when it’s more passive (glasses, for example).

ElCapitan said:

There is large number of open-source libraries in use, and both closed source and open source applications built on these running on macOS where it is highly unlikely they will ever be ported to ARM. Many of these run on the current macOS by a shoe-string only by feature of running on Intel, as the port is relative untrivial compared to a port to ARM.

You're missing the crucial aspect of Open Source software:  the source code is ...open.

The ones that are needed will come along.   As needed.   

Don't conflate iOS and ARM Macintosh.  The article does that by implication at least. 

There's no additional benefit to iOS developers in ARM coming to the Mac.  That's not a bad thing, it just is.   

The world is a lot different from 2005, and a different *PLANET* from when the move was made from 68K to PPC.  In both those cases, Apple had change management strategies in place, and minimized -- with varying success -- the complexity exposed to developers.   Ironically, some developers were angered by that.

The thing about Apple is, if they want it to happen it will happen.  They won't focus group it. They won't manage the rate of change over based on customer perceptions.  They'll do it according to what's best overall and in the long run.  They always favor the strategic.  During the Intel changeover, it went so well they just went ahead and pulled the trigger. That wasn't a reaction to customer perceptions, it just WAS.

As it was for intel, all the Frameworks are already being built for ARM..not because most of the frameworks already also exist for iOS, but because Apple's surely been expecting this changeover for a long long time.  Almost all functionality exists on all platforms in early identical ways:  Metal, the GPU framework, displays everything, accelerates nearly everything, and is everywhere.  Image handling, networking, file management, maps, location, webkit, mail, calendars, muslc, books, messages...

So the biggest issues in the past and also the biggest issues now for developers are business-related.  Either they don't have the resources or they're no longer around -- or both -- to update their apps.   And a BIG BIG part of that is customers.  They'll tell you a certain plugin is CRUCIAL to their workflows and then in the same breath tell you they'll never pay a developer for updates.   They'll never pay more than 99 cents for an app. That all software should be free.   Blah blah blah.  People suck when it comes to paying money for software.  

THAT'S where a huge part of the pain for developers is.  

I trust OpenID if they say there are security holes. And given the importance and visibility to Apple, I’m sure they’ll address the security issues before releasing SIWA. 

‘As for compatibility with generic OpenID?  Nice for OpenID, but it would only muddy the waters when it comes to customers understanding what SIWA is all about. Id be surprised if Apple makes that a priority. 

AppleExposed said:

Well, this is the only explanation I could think of why an iMac refresh is taking so long.

Although I can dream these benchmarks are for a new Apple TV.

AppleTV already has the A8. What about an Apple TV is lacking in performance? I doubt AppleTV would ever get something like this. It may get a refresh to A11 or later, but that will be to make it easier on developers who use hand-rolled Metal code. (A11 architecture brought significant changes/advances to how Metal code is written).