They might sell more iPads, but iPad sales are not growing any longer.
That's been true for about 4 years now. There might be a very small bounce here after hitting the bottom in Q2 2017, but its effectively flat.
They are growing. If look at the 4 year beginning and ending window they aren't but last 12-18 months they have. Apple's delusion that they have high price elasticity is what they corrected. There is a "low cost" iPad now to deal with the damage that Chromebooks and Windows S type alternatives are offering. Amazon is also healthily taking chunks at the low end consumption end.
That Kuo predicts a revised iPad mini with a lower cost screen ( and likely lower than current "low cost" iPad ) should put the iPad product line as a whole back on track. Trying to retreat into ever more expensive "Pro" iPads (dramatically driving up the average selling price) is a bad solution when competitors are beating you on better value proposition. Apple needs both. Ignoring the minis ( iPad and Mac) and the entry Mac laptops ( MacBook Air) has problems. Dropping the iPhone SE off a cliff is probably going to bite them in the butt in a couple of years too. Apple probably doesn't like looking at those but selling every more expensive stuff can easily turn into a death spiral.
Phablets are phones so that means they have a monthly service cost. A wi-fi iPad mini doesn't. The lifecycle ownership costs are substantially different. What Apple should have seen was that most folks were not going to dump their iPads on a 24 month cycles ( many folks aren't even doing that for phones now either).
To loop back tot he Mac Pro, Apple needs to put a line in the sand on its cost. A Mac Pro baseline price higher than the iMac Pro would be self destructive move. Even moving the base price deep into the $3K range is highly dubious. If they want to tank the overall revenues over the long term there are few thing they could do have have a worse negative effect on sales and revenues.
I would also be skeptical that the iPad line gets more play than the Mac line at this event. The iPad will probably open (after the usual pat yourself on the back moments), but the Mac line has potentially every single computer outside the MacBook Pro to talk about: Air, Mini, MacBook, iMac, iMac Pro and Mac Pro. And probably in that order of likelihood of appearing and amount of time given if introduced at all.
Depends upon whether they also do a iPad mini now rather than later. Kuo's prediction seem to lean on later but if it is sooner rather than later the iPads will get more time budget. It isn't just iPad. If Apple has a new pencil that will likely take up demo time. If they have to explain that the new pencil is "Pro" only... a little bit more.
I don't think Apple is going to break out the iMac Pro here. If the Mac Pro isn't ready and it is extremely likely that the iMac Pro isn't ready for a bump either. If can see them both being lumped into a 'come back in December and will have more to say' line, but details seems doubtful.
I doubt the MacBook is going to take long at all. ( There may not even be an update. Amber Lake brings No Meltdown/Spectre fixes. No GPU update. only some better binned dies for small clock bumps which probably means no gain in battery life. ). The one system in the Mac line that might be on balance better off with an Apple A-series is this 'one port wonder' design. I can see Apple letting that coast for another 6-10 months until perhaps Intel gets their 10nm production cleaned up for limited high volume.
True, but as you can tell. Even if consumer things move to 10nm sometime soon, there will be plenty of 14nm chips being produced for some time, including the chipsets.
Chipsets is part of what the capacity build out is for. From the $1B investment article I had liked in before another quote.
"...In particular, the company had to develop 22-nm new version of its H310C chipset in a bid to free up its 14 nm capacity, according to
Tom’s Hardware. .."
The log jam on 14nm is screwing up their chipset roadmaps too. Even if intel moves some CPUs off of 14nm (e.g., Y-series mobile since they are 'smallest' ) then they still have chipsets were scheduled to drop onto 14nm to soak up a large portion of that vacated space. Intel's FPGA business is has an even bigger problem than the CPU line up in that it needs to get onto a good 10nm process in a bigger way ( more competition. ). The cell phone modem is also in worse shape. ( they'll get a bump out of this and maybe next years iPhone but being behind on process is going to hurt later. And it is alot easier for Apple to dump them there. )
Also, there are market competition issues at hand. If Intel doesn't boost capacity soon, they supply issues might lead to loosing contracts to AMDs fairly competitive CPUs and once people start transitioning it may be hard to win them back.
Intel is going to loose some to AMD anyway. Intel's pricing as much as their 10nm woes is going to cause that to happen. In the server space it Intel has some advantages in some subsets and AMD has some advantages on a substantively different subset. There is definite overlap, but there are also differences.
That uptick in AMD is actually going to be a bit of a relief value for Intel's log jam. Tactically if they maneuver their stronger products through behind their weaker products they should do OK and AMD's encroachment will be capped.
Intel isn't going to have too hard of time keeping up with AMD on performance in a pure sense, but if they can't supply them, it doesn't matter.
In GPU computation space yes they do. They will make up bigger chunks in about 18-24 months but for now they are running a big deficit. As for as x86 core counts. It will be a challenge for those who don't care about NUMA effects. It probably should tip a bit negative in late 2019 - late 2020.
For the Mac product context, they are probably not going to be too far apart.
Optane DIMMs would be expensive, true. But getting up to 512 GB out of a single DIMM and being able to populate the other DIMMs with standard DDR4... whoa. That opens a TON of doors for relatively small footprint computers with low overall costs otherwise. I don't think we've seen prices yet, but many users won't be particularly price sensitive if it does something that ordinarily would require a server with 16 DIMM slots to be populated with lots of not-cheap-either DDR4. I'd certainly be sad if Apple couldn't bother to support Apache Ridge. Enough so, they might lose 10s of thousands of dollars of sales from me.
This will likely run into similar problems the "dual GPUs" ran into with the Mac Pro 2013. The high level software programs will have to adapt a bit and many won't. A few will but is that enough to motivate Apple to do kernel changes that only get to the Mac Pro (and perhaps the iMac Pro). Intel may also kneecap the W series on this feature also.
Far more off the shelf apps could adapt to an Optane M.2 SSD scratch drive slot than to the Optane DIMMs with zero changes to kernel or app.
I think Intel will bring Apache Ridge functionality down to the Xeon W level but not before the next socket change ( or perhaps socket
and 10+++ nm change) . It would be dubious for Apple to wait for that for the Mac Pro. They should start to scoping the work to put it in later at this point though so it can be ready 18-24 months from now. If they were now getting massively sidetracked with porting macOS over to ARM for a 2020 target for some lower corner case Mac products , then that probably wouldn't happen.
There are just
WAY too many usecases where just a reasonably up to date Mac Pro would have leverage than to chase this relatively narrow niche. As Intel makes it easier to get into and expand, Apple should do that. But this bleeding edge and small , that isn't really what they do best. if Apple could master 8 DIMM slots on one CPU package that would be very good progress in and of itself. They could move one from that solid foundation.
[doublepost=1540580639][/doublepost]
AMD is going to need a different set of drivers but I think the kernel already runs on AMD? I don't think they'd have to fork it. I'm not even sure the kernel needs any AMD specific code to run.
fork probably was too narrow a meaning in that concept. It wasn't necessarily a complete different line of code development. It was more so that were going to need to branch (fork) the resources and development process also. A scheduler for a high NUMA system isn't the same scheduler for a 2-4 core laptop, or 2 core low energy phone.
Microsoft has substantive modified kernels to run windows on this 886 core beast then they have on running their Surface products.
https://www.anandtech.com/show/1352...x86-datacenter-class-machines-running-windows
covering all of those spaces requires more resources ( people , equipment , and time ). That is more so the 'fork' I was trying to get at.
AMD NUMA is different than Intel NUMA even at the same product levels. Apple could throw an unoptimized kernel at those CPU packages that 'worked' (as in booted and ran), but they won't be strictly competitive running at the top end if other folks (Linux/Windows) are running tuned kernels and Apple isn't.