News for hackers. Stuff that matters.
Re:Intel delays Cannonlake 10nm processor for the third time by Slartie on Wednesday September 20, 2017 @10:48AM (#15294329)
So I guess this means that we'll have to wait an additional year for the MacBook Pro that finally smashes through this archaic limit of 16 gigabytes of memory :(

Except if Intel wakes up and relieves us from our pains by inserting a Kaby Lake revision of sorts with an updated memory controller capable of driving more low-power RAM. I personally couldn't care less about 10-20% more processing power per watt from Cannonlake and 10nm, it's the memory limit that's really limiting me.

Re:Intel delays Cannonlake 10nm processor for the third time by glhaynes on Wednesday September 20, 2017 @10:57AM (#15294419)
Add one more to the "Reasons Apple would want to take control of their own destiny by putting their own chips in Macs" tally.
Re:Intel delays Cannonlake 10nm processor for the third time by marricks on Wednesday September 20, 2017 @11:57AM (#15295212)
Not to mention they've already done something similar when they switched chips from Power PC to Intel. I find it hard to see how they'd license x86, but who knows, they do have ridiculous amounts of money piled up...
Re:Intel delays Cannonlake 10nm processor for the third time by slezyr on Wednesday September 20, 2017 @01:38PM (#15296315)
I think it's easier for them to turn iPad + iOS into laptop that make a x86 processor.
Re:Intel delays Cannonlake 10nm processor for the third time by ChrisLTD on Wednesday September 20, 2017 @12:21PM (#15295513)
... and unfortunately they aren’t likely to spend it on the Mac given the size of the market. Makes me sad.
Re:Intel delays Cannonlake 10nm processor for the third time by runeks on Wednesday September 20, 2017 @11:40AM (#15294988)
But how many x86 legacy Mac apps would break if they switched to ARM?

Could it be the case that we’re really waiting on Apple’s lawyer team to figure out how to sidestep Intel’s x86 patent, so OSX can emulate x86 with a bunch of ARM chips?

Re:Intel delays Cannonlake 10nm processor for the third time by erikj on Wednesday September 20, 2017 @11:58AM (#15295217)
Apple doesn't seem to care much about legacy software given their recent history. They could revive their Rosetta binary translator.
Re:Intel delays Cannonlake 10nm processor for the third time by pcwalton on Wednesday September 20, 2017 @01:02PM (#15295956)
Intel is litigious when it comes to emulating x86.
Re:Intel delays Cannonlake 10nm processor for the third time by masklinn on Wednesday September 20, 2017 @01:16PM (#15296090)
The biggest issue is likely that they don't have performance headroom they could spend on the emulation though, x86-on-ARM would be way slower than Rosetta let alone m68k
Re:Intel delays Cannonlake 10nm processor for the third time by Skunkleton on Wednesday September 20, 2017 @01:29PM (#15296221)
Re:Intel delays Cannonlake 10nm processor for the third time by bogomipz on Wednesday September 20, 2017 @11:01AM (#15294471)
>"So I guess this means that we'll have to wait an additional year for the MacBook Pro that finally smashes through this archaic limit of 16 gigabytes of memory."

Can you elaborate? What are the details of the current chips that limits Macbooks to 16 Gigs? Is it power consumption?

Re:Intel delays Cannonlake 10nm processor for the third time by masklinn on Wednesday September 20, 2017 @11:03AM (#15294494)
16GB is the limit on LPDDR3 (not sure whether it's spec or Intel's implementation), so you can pick either battery life and 16GB with LPDDR3 or 32+ at the cost of battery life (and a mainboard redesign) with desktop-class DDR4.
Re:Intel delays Cannonlake 10nm processor for the third time by snuxoll on Wednesday September 20, 2017 @11:34AM (#15294908)
The DDR3 spec limits each individual DRAM chip to 8Gb (Gigabits, not bytes) - 8 individual chips makes up a full 64-bit bus, so for 16GB of total memory Apple needs 16x8Gb DDR3 chips in the notebook. I'm not sure if Intel CPU's are limited to 16 individual DRAM chips when used with LPDDR3, but even if they COULD be used with 32x8Gb modules it would suck up a lot more power.

DDR4 allows FOUR times the capacity on the same amount of individual chips, instead of a full dual-rank DIMM capping out at 16GB like DDR3 they can be up to 64GB. On the MacBook line with LPDDR4, assuming the same 16 chip limit, you would also be able to configure it with up to 64GB (16x32Gb).

Re:Intel delays Cannonlake 10nm processor for the third time by chx on Wednesday September 20, 2017 @12:09PM (#15295352)
https://www.micron.com/products/dram/lpdram hrm? There are no LPDDR3 sizes which do not have a LPDDR4 counterpart. What am I missing?
Re:Intel delays Cannonlake 10nm processor for the third time by TazeTSchnitzel on Wednesday September 20, 2017 @12:22PM (#15295524)
See snuxoll's comment below.
Re:Intel delays Cannonlake 10nm processor for the third time by masklinn on Wednesday September 20, 2017 @12:05PM (#15295296)
Thank you for the expansion/clarification.
Re:Intel delays Cannonlake 10nm processor for the third time by dsp1234 on Wednesday September 20, 2017 @11:17AM (#15294669)
Micron makes, at least, 32GB LPDDR3 modules.

https://www.micron.com/products/dram/lpdram/32Gb#/technology...

Re:Intel delays Cannonlake 10nm processor for the third time by snuxoll on Wednesday September 20, 2017 @11:38AM (#15294953)
Gb != GB, those are 4GB full-width (x64) modules, making them 512MB per x8 chip, half the size of what Apple already uses in the MBP line's fully maxed out configuration.
Re:Intel delays Cannonlake 10nm processor for the third time by wyldfire on Wednesday September 20, 2017 @11:24AM (#15294779)
Those are individual 32 Gb (gigabit) ICs for use on memory modules (which contain an array of such ICs).
Re:Intel delays Cannonlake 10nm processor for the third time by dijit on Wednesday September 20, 2017 @11:24AM (#15294765)
But the CPU can't support the "LP-ness" of it.
Re:Intel delays Cannonlake 10nm processor for the third time by mamon on Wednesday September 20, 2017 @01:29PM (#15296219)
Most laptop manufacturers choose the latter option and have sales numbers to prove them right :)
Re:Intel delays Cannonlake 10nm processor for the third time by rbanffy on Wednesday September 20, 2017 @11:23AM (#15294762)
Why not multiple channels?
Re:Intel delays Cannonlake 10nm processor for the third time by snuxoll on Wednesday September 20, 2017 @11:40AM (#15294973)
Presumably they're already running it in a multi channel configuration, I don't have a modern MBP to check with but you need 8 individual DRAM chips per DIMM (or soldered on equivalent). Since the JEDEC spec for DDR3 caps each individual chip at 8Gb (1GB) they'll have 16 of them, which are probably run in dual-channel instead of dual-rank single-channel.
Re:Intel delays Cannonlake 10nm processor for the third time by pasbesoin on Saturday September 23, 2017 @05:22PM (#15321797)
With the reported performance of the A11 in the new iPhones, my speculation remains that Apple may well be moving to an in-house MacBook (Pro, and whatever) CPU/GPU system.

I don't know what that would mean with respect to system memory. IIRC, I read that the iPhone 8 comes with 2 GB of RAM. But, its predecessor, the 7, doesn't seem to be lacking, despite this.

Re:Intel delays Cannonlake 10nm processor for the third time by masklinn on Wednesday September 20, 2017 @11:01AM (#15294473)
What I can't help but wonder is: is the 16GB LPDDR3 limit one of spec or implementation? And will an eventual support for LPDDR4 simply bump the hard limit up to 32GB?
Re:Intel delays Cannonlake 10nm processor for the third time by jarym on Wednesday September 20, 2017 @12:10PM (#15295377)
The other option Apple might consider by then is keep RAM at 8/16Gb but offer an Optane module in addition? Dunno if that'll be viable but it might be a better option.
Re:Intel delays Cannonlake 10nm processor for the third time by fhood on Wednesday September 20, 2017 @10:56AM (#15294411)
I am honestly shocked that it hasn't happened already. Apple must be leaning on them pretty hard
Re:Intel delays Cannonlake 10nm processor for the third time by Slartie on Wednesday September 20, 2017 @11:01AM (#15294470)
It's not even only Apple anymore. As far as I have seen, the Microsoft Surface Pro suffers from the exact same limitation. Practically every manufacturer who wants to build some high-end, but still thin and lightweight laptop runs into this problem.
Re:Intel delays Cannonlake 10nm processor for the third time by cjbillington on Wednesday September 20, 2017 @04:17PM (#15297819)
What's the deal with the dell xps 15 and precision 5520 laptops then? They're 15 inch but they're still pretty thin and light (1.78kg for the precision 5520), but you can get them with 32 GB of RAM and their battery life apparently isn't terrible. I'm planning on getting one and never realised this was a compromise.
Re:Intel delays Cannonlake 10nm processor for the third time by RivieraKid on Wednesday September 20, 2017 @04:59PM (#15298191)
What do you need more than 16GB for? Until less then a year ago, I used to have a 4 GB RAM (+ 4GB SSD swap) laptop, used it for everything, including software development (Android mostly). Even ran virtual machines occasionally. It wasn't that horrible.

Now I have a MacBook Pro with 16GB and this amount seems more than comfortable.

Re:Intel delays Cannonlake 10nm processor for the third time by kakarot on Wednesday September 20, 2017 @06:34PM (#15298965)
Video and image processing/editing, for starters. Working with large datasets. Running several vms with reasonable memory allocation. Running local DBs. High-end / VR gaming. Etc. I do all of these things daily for both work and pleasure and with 16GB RAM I have run into countless headaches.

Personally I don't use a Mac and could upgrade at any time but I'm waiting out of principle because DDR4 RAM is still seeing exorbitant prices from the shortage.

Re:Intel delays Cannonlake 10nm processor for the third time by milesokeefe on Wednesday September 20, 2017 @06:34PM (#15298961)
Right now on my MPB I'm sitting at 14.68GB used with another 3.73GB in swap. Between Chrome, electron-based desktop apps, and Docker containers it's easy to hit that limit. This is just full stack web dev too, nothing rendering related.