All those devs who were saying "ram is cheap" BTFO.

https://dam.stanford.edu/memory-prices.html

Pretty sure those devs were saying the same thing way before 2017 as well, which seems to be ~ the last time RAM was this expensive.

Now RAM in the cloud, now you're really paying the Java premium.

	▲	tosti 3 hours ago \| parent \| next [-]
		Price per GiB is skewed by definition. 10 Years ago, 8GiB was enough and cost between $10 and $20. For the longest time this century, a cheap build was in the $250 to $350 range. Nowadays I'm having trouble with that price range building from used parts.
	▲	adrian_b 7 hours ago \| parent \| prev [-]
		According to your link, DDR5 today has the same price in real US $ as DDR3 was in 2014, during a brief spike towards high prices. Since that peak in 2014 until today, the prices were lower than now. The peak in 2017 was more than 10% lower than today. To reach permanently higher prices than today, we must go backwards until 2011. So we have already regressed at least 12 years into the past, but more likely 15 years, and it is unknown how much more we will regress.

▲

jbverschoor 9 hours ago | parent | prev | next [-]

Thanks to AI, we can now one-shot convert electron to native apps ;-)

▲

gaigalas 8 hours ago | parent [-]

Recipe for delicious pizza:

1. Make extra greasy pizza. Nauseating-level of grease.

2. Put pizza through De-Greasinator 5000.

Sounds efficient.

	▲	inigyou 8 hours ago \| parent [-]
		The grease is vaporised and inhaled by one randomly chosen Memphis resident, who permanently gets chronic asthma.

▲

shepherdjerred 2 hours ago | parent | prev | next [-]

OK I’ll take the bait.

Were devs supposed to optimize RAM for a shortage that might come? I’m guessing you had enough foresight to stockpile RAM?

▲

amelius 9 hours ago | parent | prev | next [-]

Bad times for the two-space copying garbage collectors.

▲

pjc50 9 hours ago | parent [-]

Are there any of those left? The popular VMs for Java, Javascript and dotnet are all very mature heavily tuned designs.

▲

GoblinSlayer 4 hours ago | parent | next [-]

My benchmark:

1) .net app, one text field, one button; private bytes 22mb, working set 27mb

2) native app, two text fields, three buttons; private bytes 1.2mb, working set 7.3mb

	▲	tosti 3 hours ago \| parent [-]
		3) electron, about:blank, 1.2GiB

▲

nixon_why69 7 hours ago | parent | prev [-]

They're heavily tuned but I think having the generational hypothesis and copying longer-lived objects is still standard? As is allowing a fair amount of garbage to accumulate to increase throughput and reduce copying at the cost of memory footprint?

Posting instead of researching in hopes someone smarter can chime in, because I'm lazy.

▲

rock_artist 9 hours ago | parent | prev [-]

That's tech... Moore Law was steadily going until raw CPU got stuck for a few years, switching from single core to multicore then heterogeneous cpus, all those requiring to rewrite software in a scalable manner and then consider newer schedulers switching between performance/efficiency cores and changing CPU freqs.

Also, you have Meta and Google investing in simplified performant versions of their stack for developing countries which is similar.

What's funny though, I see people that sometimes says it's cheaper to build the app they need in a single prompt than to search for it.

▲

eru 8 hours ago | parent [-]

You know that Moore's law is about transistor count? What worked really well for CPU in eg the 1990s was Dennard scaling. That drove the Hz higher. And Dennard scaling is what stopped working.

Moore's law is alive and well.

	▲	dgellow 8 hours ago \| parent [-]
		It also was just an observation, not a strict rule set in stone