Earlier quoted context omitted.
Exactly. It's not an apples-to-apples comparison. 8GB of M1 RAM is very different than 32GB of standard DIMM-like RAM. Sort of like when people compare nm of processes on the chips. You can't just say "oh, their number is smaller, it must be better." To be sure a device with 16GB of M1 RAM should be more competent than 8GB of M1 RAM, but now that's apples to apples.
> 8GB of M1 RAM is very different than 32GB of standard DIMM-like RAM. Go on... What’s the nature of this great difference?
Apple’s M1 Positioning Mocks the Entire x86 Business Model
501–510 of 942 posts
Re: Apple’s M1 Positioning Mocks the Entire x86 Business Model
#502Earlier quoted context omitted.
Pretty sure that Apple considers this a feature.
Funny. Except there are fully supported MacBooks from 2013 running the latest version of macOS, still on their first battery, still bringing people joy and productivity.
Re: Apple’s M1 Positioning Mocks the Entire x86 Business Model
#503Earlier quoted context omitted.
So my sister does professional photography, and went from a 16GB MacBook Pro(2016) to an 8GB Air, and reports no decrease of productivity - quite the opposite, in her experience all Adobe programs run much faster, and the machine is quieter and lighter to boot. So yeah, I'm not sure - maybe the ram amount isn't as a big deal as people make it out to be. On the other hand I'm a C++ programer and my workstation has 128…
> I'm a C++ programer and my workstation has 128GB of ram and I wouldn't accept any less What on earth are you programming?
128gb is likely overkill, but I can see a use case depending on what you're doing.
Re: Apple’s M1 Positioning Mocks the Entire x86 Business Model
#504Earlier quoted context omitted.
Yep, if you're running big IDEs (e.g. Rider/IntelliJ, Visual Studio), containers and VMs, 32GB is really a must. There always seem to be people in these threads claiming that 16GB or even 8GB is enough - I just don't understand how that could possibly be for most of the HN demographic.
Do you think most of the HN demographic is actually running big IDEs, containers and VMs at the same time? I'm personally a CS student and never had to run more than a few lightweight docker containers + maybe one running some kind of database + VS Code and that has been working fine on a laptop with 8GB and pop_os. Could imagine that a lot of other people on HN are also just generally interested in tech but not nece…
Re: Apple’s M1 Positioning Mocks the Entire x86 Business Model
#505Earlier quoted context omitted.
Yeah the marketing effort is immense, and it's really surprising to me how many eagerly lap up the angle Apple is pushing without much reflection, even on HN. Like the good old Apple hype days. Now to be fair, the M1 is an impressive iteration on the A* chip line. But the Ryzen 5000 mobile chips really don't look bad at all in comparison, and a 5nm version of those would level the field.
I didn’t buy the hype until I tested an actual M1. It exceeded the hype. It feels like when I was a kid and went from a 386SX to a Pentium at 4X the speed, except the M1 was also a quarter the power consumption. It’s the first time in a over a decade I’ve felt a revolutionary step forward in a chip and the only time it has ever come with less power. Process node is a factor but I find it hard to believe it’s the only…
Re: Apple’s M1 Positioning Mocks the Entire x86 Business Model
#506Earlier quoted context omitted.
I can't ever imagine why manufactures of > don't use dates. Product lines 1 - 10. Bigger is better. A minimal number of qualifiers next to the numbers, ideally just 1 of them next to a product line number (Pro/Home/Hobby/Enterprise/whatever). Date, month and year format if you really want flexibility. OblioCorp Oblio 1 Home 2020.06. Oblio 10 Enterprise 2021.04. How hard is that? Not that hard, from where I'm standing…
Because approximately no one in the whole supply chain wants to be stuck with a part dated last year. And product lines are speced 12 months in advance. So you need precise demand prediction all the way along your supply chain for this to work.
Apple never says iPad 2019 on their website, until you start digging really hard.
Re: Apple’s M1 Positioning Mocks the Entire x86 Business Model
#507Earlier quoted context omitted.
Yes, this point is so obvious, I feel like I've got to be missing something. I am a professional programmer. I am vaguely aware that Intel chips have X-Lake based codenames. I have no idea how to compare the chip in my current laptop to a new laptop based on Intel's marketing names. To convince myself to upgrade, I just go to Geekbench, because nothing else in the marketing tells me the new chip is better. Seems like…
Intel CPU numbering: iX-YYZZZ[Suffix] X = 3/5/7/9 = market positioning bucket. Higher is better Y = generation, currently at 11. This is basically a numeric form of the "* Lake" naming, except for 10th gen where Ice Lake (10nm, better power efficiency) and Comet Lake (14nm, higher max perf) co-existed in laptops ZZZ = position within that generation, higher is better, more detailed than the i3/i5/i7/i9 bucketing. Suf…
Re: Apple’s M1 Positioning Mocks the Entire x86 Business Model
#508Those are all the same chiplets, just binned differently. High performance ones go into the 5800x and 5950x. Lower performance ones into the 5600x and 5900x.
Which seems to be the same thing apple does, with a slight naming difference. Calling everything M1, instead of naming the CPUs.
Re: Apple’s M1 Positioning Mocks the Entire x86 Business Model
#509Earlier quoted context omitted.
Yes, this point is so obvious, I feel like I've got to be missing something. I am a professional programmer. I am vaguely aware that Intel chips have X-Lake based codenames. I have no idea how to compare the chip in my current laptop to a new laptop based on Intel's marketing names. To convince myself to upgrade, I just go to Geekbench, because nothing else in the marketing tells me the new chip is better. Seems like…
Intel CPU numbering: iX-YYZZZ[Suffix] X = 3/5/7/9 = market positioning bucket. Higher is better Y = generation, currently at 11. This is basically a numeric form of the "* Lake" naming, except for 10th gen where Ice Lake (10nm, better power efficiency) and Comet Lake (14nm, higher max perf) co-existed in laptops ZZZ = position within that generation, higher is better, more detailed than the i3/i5/i7/i9 bucketing. Suf…
https://ark.intel.com/content/www/us/en/ark/products/69114/i...
Re: Apple’s M1 Positioning Mocks the Entire x86 Business Model
#510Earlier quoted context omitted.
The parent comment didn’t say “we’ll all be using Apple” He said ARM.
I edited my comment as I think in the context of the larger discussion, ARM and Apple are basically interchangeable.
[0] https://dev.to/dnx/arm-vs-intel-a-real-world-comparison-usin...