Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Why is it that when Apple was a 10th the size they did 10x more stuff. But now they are a supergaint, they can barely refresh a single product line? My guess is the administration is bloated behind closed doors, trying to implement all these tertiary programs that gum up time. Nothing good has every been achieved my men who spend thier lives in a suit.

eh?

Apple had computers, airports and ipods back then.

Now they have:
computers, iphones, ipads, watches, homepods, airpods, icloud, maps, siri, and no doubt AR/VR hardware coming.

Apple are doing much, much more today than ever before.
[doublepost=1527670851][/doublepost]
No, Apple cannot "handle this". Not without forsaking power users, at least. Emulation (aka Rosetta) carries a notoriously high performance penalty. x86 and ARM require fundamentally different and mutually exclusive approaches to performance. Furthermore, Intel is the world leader in fab tech. Go read any article about CPU architecture on Anandtech.com- those guys are seriously talented in writing in such a way as to make tech accessible to the masses.

Yes.

There's a penalty.

But all the frameworks used by an application will already be native. Most of the hard work an app does these days is done by the apple frameworks.

2d: quartz (native), spritekit (native), core graphics (native) etc.
3d: metal (native)
AR: arkit (native)
math: openCL or metal (native)
UI: cocoa (native)
... you get the picture.

The only non-native code in the application will be application logic and for most applications that's a LOT less than you might suspect these days. So much of it is telling the frameworks what to do with objects, and all that is native code.

If say 70% of the code running is native frameworks, and 30% of the code run time is spent in non-native code, the gains you get running the native code faster can help offset the performance decrease of the smaller non-native fraction.

They did it before. PPC and x86 were extremely different.

They have a lot more stuff already native than before.

The power users will continue to get intel until there's a lot of stuff ported. But it won't take anywhere near as long as some might think for that to happen. So much of the running code will already be native purely due to running the application on an ARM copy of macOS.


edit:
to clarify, in case some don't realize. an application running on macOS doesn't just run code contained within itself. huge amounts (i'd wager: most) of the code running in a modern application is actually the frameworks and data. theres glue code in the application that tells the OS frameworks to instantiate objects (calling into native code) and tells them what to do. with their mostly native methods.

Yes, not 100% of the application code is doing that, but a huge amount is.
 
Last edited:
I'm talking worthwhile upgrades overall - not just from Apple's perspective
LPDDR is extremely worthwhile for the entire mobile market, not just Apple. It allows not only for 32GB, but also for a 33% increase in data rates over DDR4 plus the extremely handy (especially for mobile devices) ability to not kill your battery on standby.
 
Apple had computers, airports and ipods back then.

They also had:
iSight
Monitors
Printers
SuperDrive
Scanners
Palm tablet
Xserve
Mac mini
Time capsule
airport

They might be doing more today when you count their software and services, but they had plenty of work before as they were focused more on competing against HP, Dell, etc. Today, they simply pivoted to a different business model. In my mind they are still a hardware company though
[doublepost=1527687430][/doublepost]
huge amounts (i'd wager: most) of the code running in a modern application is actually the frameworks and data. theres glue code in the application that tells the OS frameworks to instantiate objects (calling into native code) and tells them what to do. with their mostly native methods

Right except instructions are built and compiled with a certain chip architecture in mind for optimizations . If there needs to be a translator layer that sits between x86 and converts it to ARM instructions it’s going to incur performance penalties.

I’m probably barking up the wrong tree considering there are no real performance Mac apps for the most part

The only thing I can think of right now is you would have to rebuild your apps.

Granted this doesn’t even take into consideration people like me who work out of the Terminal using gcc/g++
 
Laptops and iMac make up 90-95% of Mac sales and are updated every year with few exceptions, depending on Intel release schedules.

Mac Pro hasn’t been updated since 2013 due mostly to being rather mis-managed as a product line. Secondarily, low sales due in no small part to high end iMacs—even before iMac Pro—cannibalizing sales.

Mac mini hasn’t been updated mostly because sales are so low.

Sales are so low because it has not been updated! Even the 2014 update was disgusting. They got rid of the quad core cpu and replaced it with the dual core. The entry level got the handicapped 1ghz processor. You can't expect sales to go up when it's the worst product you give. The higher end mini which is a dual core i7 with 16gb and 1tb drive is 1700$ CDN + tax .. which is a joke nobody with a sane mind would buy that. At the time, I recommended a mini to my brother (we added ram, added SSD) and it's still running great but the newer one is slower and you can't upgrade it.

The iMac (except for 2016) and macbook lines were the only ones that received updates.

They failed to refresh the monitor, the routers, the time machine, the mini, their server, the Mac Pro. Like many others, I stopped recommending them. If you don't mind the price the macbook are decent but the cheapest one is 2000$

I don't care the cpu brand they use as long as I can see a value in the product.
 
  • Like
Reactions: Yvan256
Overstatement of the year. I'd say it's been downright chilly, and for good reason.

This, it *looks* cool but it's actually really irritating to use. I do like the fingerprint scanner, wish you could get an escape key edition MBP that had the standard F* keys and it, alone (or, hell, I'd be ok with the full row of F* keys and the touchbar on top, then it's just an auxiliary toolbar, not a cruddy replacement for a useful row of keys)
 
  • Like
Reactions: Yvan256
Windows 10 is capable of running on ARM, so I'd think so.

This could be a great way of getting Mac prices to come down. I wonder how much of the current price is solely having to pay Intel their exorbitant prices?
[doublepost=1527602417][/doublepost]

No. The compiler would have to be capable of compiling down to ARM, but it already is because they use the same compilers for both macOS and iOS (and tvOS and watchOS and their other OSs that run on ARM.)

All other computer manufacturers have their prices lower than Apple, so I don't think its Intel's exorbitant prices that makes Apple hardware expensive.

Also, I meant 3rd party software like Office, Adobe, Evernote, LibreOffice..etc
 
  • Like
Reactions: navaira
Also, I meant 3rd party software like Office, Adobe, Evernote, LibreOffice..etc

Right. They're already using Apple's compiler, so all they have to do is change a parameter in their build tool to say ARM instead of x64 and they'll be all set. Code won't need to change.

And some of those might be running in virtual machines which came with macOS (IE, Python) or are easy enough to install (IE, Java) so only those VMs need to be recompiled.

Plus, actually, I think Apple has required that all Mac App Store uploads be in a CPU agnostic format, so Apple can handle automatically recompiling them all for ARM without involving the developer, in the case of apps you get from there.

This transition should be pretty painless. At most it'll take a person day per application.
 
  • Like
Reactions: throAU and Yvan256
They also had:
iSight
Monitors
Printers
SuperDrive
Scanners
Palm tablet
Xserve
Mac mini
Time capsule
airport

They might be doing more today when you count their software and services, but they had plenty of work before as they were focused more on competing against HP, Dell, etc. Today, they simply pivoted to a different business model. In my mind they are still a hardware company though
[doublepost=1527687430][/doublepost]

Right except instructions are built and compiled with a certain chip architecture in mind for optimizations . If there needs to be a translator layer that sits between x86 and converts it to ARM instructions it’s going to incur performance penalties.

I’m probably barking up the wrong tree considering there are no real performance Mac apps for the most part

The only thing I can think of right now is you would have to rebuild your apps.

Granted this doesn’t even take into consideration people like me who work out of the Terminal using gcc/g++


Running the frameworks there will be no translator (for the work done by the framework) even if the app is not native. It calls into the OS provided native frameworks to get stuff done for a lot of the heavy work.
 
For them to even consider dumping the Mac, it’d have to dwindle enormously first - it’s still a multi billion dollar enterprise on its own, after all! If people start switching to hybrid idevices at a tremendous rate, then perhaps but I think the Mac would have to be pretty much dead on its own before they would kill it.

We’re talking within the context of ARM based Macs running the same software as iOS.

By that point it wouldn’t suprise me if Apple wants everyone to just use iOS, remember this company promoted the ipad as replacement for people running old computers.

BTW, I’m not saying this is what I want Apple to do, personally I wouldn’t buy an ARM based Mac unless circumstances made me have to.
 
I would love an ARM-based Macbook simply because I like new things. I've spent the last few years wishing there was an actual alternative to Windows, Linux, macOS. I wonder what they're going to do with the convergence (or lack thereof) of macOS and iOS for such a machine.

But I need to be able to run Scrivener, Creative Cloud software, Reason, Evernote. I don't mind no Windows. But if all it runs is App Store software (and trust macOS 10.14 to keep crashing the ARM software versions until 10.16 is released), I'm not interested... unless it's got awesome keyboard and costs €299.
 
  • Like
Reactions: eVolcre
I would love an ARM-based Macbook simply because I like new things. I've spent the last few years wishing there was an actual alternative to Windows, Linux, macOS. I wonder what they're going to do with the convergence (or lack thereof) of macOS and iOS for such a machine.

But I need to be able to run Scrivener, Creative Cloud software, Reason, Evernote. I don't mind no Windows. But if all it runs is App Store software (and trust macOS 10.14 to keep crashing the ARM software versions until 10.16 is released), I'm not interested... unless it's got awesome keyboard and costs €299.
I think that the one big sell of an ARM Mac laptop is that the battery life is going to be insane.

I've been doing light productivity tasks (ok, emailing and web) on my entry level MBP 13 2017 for about 1 1/3 hours with all of the 'out of the box' battery saving settings on and I've lost 20% of my battery. This is ridiculous.

A computer with similar performance (which admittedly isn't exactly high end) but which can pull 18 hours of light productivity tasks, is going to be very attractive to many.

I know what you mean about non-app store software. I think it's time for Apple to make their App Store terms way more attractive now to get any hold-outs onboard.

And I think that anything that runs 'macOS' is always going to be able to run software downloaded out of the App Store. It'll be up to Apple to minimise the amount of times that most people do this i.e. so maybe it'll just be things like Chrome, Firefox etc.
 
  • Like
Reactions: navaira
Right. They're already using Apple's compiler, so all they have to do is change a parameter in their build tool to say ARM instead of x64 and they'll be all set. Code won't need to change.

And some of those might be running in virtual machines which came with macOS (IE, Python) or are easy enough to install (IE, Java) so only those VMs need to be recompiled.

Plus, actually, I think Apple has required that all Mac App Store uploads be in a CPU agnostic format, so Apple can handle automatically recompiling them all for ARM without involving the developer, in the case of apps you get from there.

This transition should be pretty painless. At most it'll take a person day per application.

interesting, the transition from OS 9 to OS X was long and painful so was the PowerPC to Intel , it took some time. I remember Quark took some years to develope native OS X app.
 
to get any hold-outs onboard
Hold-outs at this point are either doing things that make your system less secure (installing their own kext's) or just don't like the model. I don't see Apple doing anything to deal with the first, and the developers that don't like the idea of a store now aren't going to suddenly like the idea in the future.
interesting, the transition from OS 9 to OS X was long and painful so was the PowerPC to Intel , it took some time. I remember Quark took some years to develope native OS X app.
The BIG difference is that back then, everyone was using whatever environment they wanted to develop code. Apple had no say and no control and had to bend over backwards to try to ensure that most of the crap would either just work OR require minimal investment. Nowadays, most developers have moved to Xcode (and if you're a macOS developer NOT using Xcode... why?). One of the greatest benefits of Xcode is that as Apple implements new developer features (like enhanced memory management/garbage collection for example), all the developer has to do is update their code with the right parameters and recompile (then a bit of testing). They get the benefits with just a little work. If Apple does their homework at the compiler/microcode level this could really be remarkably straightforward for any code that's currently in-development. For anything where the developer is not actively supporting the code anymore... well... just keep your old computer ;)
[doublepost=1527774271][/doublepost]
I wonder what they're going to do with the convergence
I think they're going to be ramping down macOS as they add more and more features to iOS. The CPU switchover allows them to do that cheaper and more efficiently.
 
That’s a ridiculous comparison - if you upgrade your CPU later you’ve bought and own two CPUs. Apple is charging you for two but only giving you one!

At any given time, there is roughly a $100 USD difference between the cost of boxed versions of the Core i5-7600K and the Core i7-7700K Apple uses in the 2017 27” iMac, there is closer to a $125 USD difference for the Core i5-7400 and Core i7-7700 Apple uses in the 21.5”. Apple charges $200 USD for either upgrade, which falls in line with the general rule of thumb of Apple charging double the amount of the actual cost difference.

Apple is not charging you for two CPUs and only giving you one, as $200 USD is not going to buy a Core i7-7700K to replace the 7600K in the 27” iMac or a Core i7-7700 to replace the Core i5-7400 in the 21.5” version.

Owning two CPUs is only useful if you can sell the first CPU or you have a second system you are building. For the majority of people, the “average consumer” if you will, it is simply a nifty paperweight.

Again, I believe what you and many others here want from Apple is a computer they have not made since 2012-2013 (Mac Pro 5,1) and in all likelihood will never make again.
 
  • Like
Reactions: throAU
At any given time, there is roughly a $100 USD difference between the cost of boxed versions of the Core i5-7600K and the Core i7-7700K Apple uses in the 2017 27” iMac, there is closer to a $125 USD difference for the Core i5-7400 and Core i7-7700 Apple uses in the 21.5”. Apple charges $200 USD for either upgrade, which falls in line with the general rule of thumb of Apple charging double the amount of the actual cost difference.

Apple is not charging you for two CPUs and only giving you one, as $200 USD is not going to buy a Core i7-7700K to replace the 7600K in the 27” iMac or a Core i7-7700 to replace the Core i5-7400 in the 21.5” version.

Owning two CPUs is only useful if you can sell the first CPU or you have a second system you are building. For the majority of people, the “average consumer” if you will, it is simply a nifty paperweight.

Again, I believe what you and many others here want from Apple is a computer they have not made since 2012-2013 (Mac Pro 5,1) and in all likelihood will never make again.

I don't want anything in particular. I was just responding to something someone else said, they said the upgrade from i5 to i7 cost as much as buying both on their own would, which I thought you'd replied to. I can't find the original post now though, so near mind!
 
Still wouldn't necessarily solve the problem radiologyman describes since the mac would still likely retain many features e.g. Finder.

i am saying ios and macos remain distinct. there is no increase in crossover. literally you can boot your phone into full native macos mode, which would require an external display and keyboard and pointing device. otherwise the phone can also boot into native ios mode. that will work even if not ideal. what specific complaint do you have with this approach?
 
i am saying ios and macos remain distinct. there is no increase in crossover. literally you can boot your phone into full native macos mode, which would require an external display and keyboard and pointing device. otherwise the phone can also boot into native ios mode. that will work even if not ideal. what specific complaint do you have with this approach?

They said macOS was complicated.
 
  • Like
Reactions: CodeJingle
They said macOS was complicated.
ios is already based on macos. they forked the original macos and stripped it down till it ran on the phone hardware that is how they shipped the first iphone.

they can fork the current ios and build it back up towards macos until it more or less is the same full kernel but built for arm instead of intel. then they can ship both ios and the arm backport of ios->macos on a split partition. the higher end iphone would have more storage and more ram.

it would take years of r&d to complete this work and what they initially ship will be slow and cumbersome to swap back and forth between the two flavors of operating system but i bet apple has already been working on this for years. sure yes macos is very complicated. once they drop 32-bit support, that reduces the amount of legacy stuff they have to support. i bet that makes the port easier. apple has been building up the ios kernel, some alignments with macos, though not necessarily in the exact direction back towards macos.

it is just a wish list item i have no proof. but if they shipped it i would buy it. it makes sense to me they would be working on this. but i could be wrong.
 
Last edited:
  • Like
Reactions: radiologyman
ios is already based on macos. they forked the original macos and stripped it down till it ran on the phone hardware that is how they shipped the first iphone.

they can fork the current ios and build it back up towards macos until it more or less is the same full kernel but built for arm instead of intel. then they can ship both ios and the arm backport of ios->macos on a split partition. the higher end iphone would have more storage and more ram.

it would take years of r&d to complete this work and what they initially ship will be slow and cumbersome to swap back and forth between the two flavors of operating system but i bet apple has already been working on this for years. sure yes macos is very complicated. once they drop 32-bit support, that reduces the amount of legacy stuff they have to support. i bet that makes the port easier. apple has been building up the ios kernel, some alignments with macos, though not necessarily in the exact direction back towards macos.

it is just a wish list item i have no proof. but if they shipped it i would buy it. it makes sense to me they would be working on this. but i could be wrong.

I doubt it was Darwin they were saying was complicated but the surface level stuff i.e. Finder, Dock, etc.

One potential option would be to allow users to switch the UI between something like Finder and Springboard, similar to Linux with no dual boot required, but this could be problematic from a UI design standpoint for software.

That said, knowing Apple they could just decide to **** with people, hiding things like the Terminal and forcing everyone to use Springboard, making the macbook into a giant ipad with a keyboard permanently attached.
 
  • Like
Reactions: CodeJingle
That said, knowing Apple they could just decide to **** with people, hiding things like the Terminal and forcing everyone to use Springboard, making the macbook into a giant ipad with a keyboard permanently attached.
They could do that. Or they could simply create an iPad in a Macbook-type shell (and distributing the internals between the screen and base halves), add support for mouse/trackpad. That would be better received by the public (than a locked-down macOS device), and cheaper to make. I'm not advocating such a move, but they could do it.
 
We have 3 MacBooks in the family of 5 and 2 of them used only as email or word processor when extensive typing is needed, which does not happen too often. Otherwise iPhones and iPads are used extensively throughout the day. I use rMB a lot due to multitasking ability and amazing engineering but what I do on it can be easily accomplished by an ARM version. I have been Windows user for 15 years prior to buying rMB in 2015 and MacOS is still hard for me to master as it feels nonintuitive.
 
Doubt it.

As per my post above, any silicon dedicated to running X64 code is dead die space once the transition happens. Apple would be better off just throwing resources at making A12X (or whatever) run all native code faster and emulate the x64 using software. The space the x64 hardware would consume would be far better used by more ARM based processor cores, cache, more GPU cores etc.

That way they don't need to debug x64 (a complex architecture) in hardware - hardware debugging and fixing is expensive. They aren't wasting die space. The performance per watt on native code will be better, the cpu will be much cheaper to make, etc. And it will be a subtle push to developers to get their code ported, rather than just providing dead-end native hardware for it to run as well as native.

If Apple and AMD were in bed on GPUs, i doubt Apple would have designed their own. Maybe Apple might license infinity fabric or HBCC tech, but that's about it. If that.

I'm an AMD fanboy as much as the next guy (I have a crossfire vega 64 setup in my PC!), but it just doesn't make sense from Apple's perspective - AMD have nothing to offer them.
[doublepost=1527644888][/doublepost]


"Yes"...
[doublepost=1527645024][/doublepost]

Mac hardware is currently crap for gaming even if you boot-camp it. There's a massive pool of iOS game developers out there who would be chomping at the bit to get their software on some proper hardware - like a high end mac A series chip.

For the cost of a Mac that runs games at any real sort of pace, you could buy a 21.5" imac AND a gaming PC. I know this, because it's what I've done. Well, replace 21.5" iMac with Macbook Pro.
[doublepost=1527645355][/doublepost]

The A10X is passively cooled. In a very tight thermal enclosure... give it better cooling and the clocks will sustain much better.



The A10X is running in a lot less than 15 watts. And was out almost 12 months ago. Time moves on. Apple won't be putting the A11X in a macbook. It will be their NEXT generation of part. With a larger die, more cores and improved tech.
[doublepost=1527645611][/doublepost]

Did you read my post where i mentioned coffee lake is the FIRST UPGRADE WORTH TAKING since sandy bridge.

Of course i know they are getting potentially a 40% performance boost. When turbo-ing. At above the chips rated TDP, which can't be sustained.

That's the first time in 8 years they've made a jump like that, apple have been getting 50-100% improvement per year, since 2008.

Too little, too late - and their onboard GPUs are crap too.

Coffee lake is the exception rather than the rule - and is 5-6 years late.
[doublepost=1527645919][/doublepost]

Yup.

Even microsoft are trying their best to kill win32. With the new metro/fluent/whatever applications. Dabbling with ARM, etc.

The fact they've moved all their stuff to 365 and are now giving first class application support (almost, give it time) to iOS and macOS is yet another signal that they're going OS-agnostic.

Microsoft are just having a more difficult time than Apple will, because they've got 30 years of hacked-together-crap in Windows to sort out, and the applications that make use of it.

Apple went through a lot of the hard work in the shift to OS X already - macOS/OSX has had the benefit of a lot of lessons learned when NEXTSTEP was developed and also since. Plus apple has been much more brutal about deprecating and removing old technology they no longer want in the platform. Microsoft has not.

Those chickens are coming back to roost now. For everyone who whines every time Apple remove stuff from macOS - this is why they do it. To enable platform shifts like this to be accomplished much more easily.

[doublepost=1527646045][/doublepost]

No, i mean coffee lake due to increased core count.

Cannon lake will be another worthwhile upgrade for Apple, however Apple has been able to use DDR4 if they wanted to make that call for years.

They didn't, and thats their call.

I'm talking worthwhile upgrades overall - not just from Apple's perspective. But even from Apple's perspective, the higher core count Coffee Lake mobile parts are a no brainer. It won't give them everything they want (no LPDDR4), but its actually more than a 5% improvement this time around.

But still an illustration of why Apple want to get off intel, long term. Apple's goals and Intel's goals don't line up well enough.
[doublepost=1527646230][/doublepost]

Remove those power, thermal and cost constraints and Apple will be able to scale their A series chips up significantly. Just as intel scale DOWN their core series.

Double the core count and 1.5x the clock speed inside of 15 watts vs. the A10X (which would be totally feasible for a 13" macbook air replacement) and you've got a monster laptop CPU...


As to "not seeing the downsides". Of course i see the downsides. There WILL be short term pain in terms of performance. But if Apple can get enough of a boost in performance from AX, they can mitigate most of it on non-native software (as they did with the intel shift) and then the following 2-3 years make significant improvements in running non-native code, and also phase out the non-native code as well - getting even more performance back.

Yes, this transition is not without pain. But apple have the pieces in place (LLVM bytecode in the store to recompile store apps natively, multi-arch binary support in macOS, rosetta technology, an amazing processor architecture) to alleviate a lot of it.

Long term, it definitely makes sense for Apple. And Apple tend to take the long view. They've got plenty of money in the bank to be able to afford to take a risk. If the new low end machine with ARM doesn't take off - so be it. But i think it will.


Will this happen at WWDC this year? I'm not sure. But i believe it will happen inside 18 months.
[doublepost=1527647105][/doublepost]

Of course. All the more reason for Apple to do it themselves.



No, just pointing out Apple's strategy. Intel can build processors for whoever they want. Doesn't mean it is in Apple's long term interests to use them.



What? Apple has sold far more laptops than desktops for about a decade.

The macbook air has been their volume seller since about 2010.

Take an A10X. Double or triple it in size (i.e., 12-18 cores). Give it actual active cooling with a fan and heatsink/heat-pipe.

You've got something that will destroy a "mainstream" desktop i7 on multi-threaded code inside of 35 watts. At far less cost to Apple.

Sure, it will perhaps take Apple a while to get the confidence to put that part out, but they could conceivably do it today. They have the tech. They have the motive. They have the money in the bank.

Apple as a company is bigger than intel... there's no reason they need to accept what intel make.


edit:
replaced A11X with A10X. got my model numbers confused. point remains.


Lol.

Called it (back in 2018) :D


(got an alert that someone liked this post :) )
 
Last edited:
  • Like
Reactions: seek3r and VulchR
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.