Apple has a memory problem and we're all paying for it

Re:Apple has a memory problem and we're all paying for it by Zanfa on Friday November 10, 2023 @01:42AM (#38215841)

I prefer my 8GB M1 Air to my 64GB Intel iMac for basically all of my Node/Rails/Swift development, with Docker running almost 100% of the time.

The only time I’ve seen the iMac be “better”, was when I had a Java project that had around 20 different packages that you needed to have open IDEs for.

[ Parent | on HN ]

Re:Apple has a memory problem and we're all paying for it by cma on Friday November 10, 2023 @04:26PM (#38224762)

How many silicon process nodes ahead is the M1 vs your intel iMac?

[ Parent | on HN ]

Re:Apple has a memory problem and we're all paying for it by Zanfa on Saturday November 11, 2023 @04:30AM (#38228763)

A few, 14nm i9-10910 vs 5nm? M1, but that's an implementation detail. The main point is that the amount of RAM is not the limiting factor.

[ Parent | on HN ]

Re:Apple has a memory problem and we're all paying for it by pxmpxm on Saturday November 11, 2023 @12:16AM (#38227841)

There is no reality where that 8gig heap machine will outperform a 64gig heap machine in any objective measure. I'm sure you will hedge with your statement with something like "well it feeels faster" or some such nonsense.

[ Parent | on HN ]

Re:Apple has a memory problem and we're all paying for it by Zanfa on Saturday November 11, 2023 @04:24AM (#38228745)

Not only does it feel faster, but it also beats the iMac at single-core performance, looking at bundle build times. If I could fully utilize all the RAM + cores of the iMac, it would obviously come out ahead, but that's not the case for most frontend dev work. Not to mention it cost about 1/3 of the iMac and the battery lasts forever.

[ Parent | on HN ]