Needing to think memory management turned out be a bit un-expected you might say. There were a few things that went well and few that were a bit unexpected.<p>Things that went well:<p>1) RAM got ridiculously cheap: 2x 8GB is now what $60-70? So it would seem, in that regard, yeah you shouldn&#x27;t care about memory.<p>2) GC languages and runtimes. Believe or not there was heavy skepticism that GC runtime could be ever be a serious strategy in practice. It was an exotic technology that many thought would left for academia and fringe research area. But most popular frameworks and languages today are GC based.<p>Some things were a bit un-expected:<p>1) Memory access speed is fast but it didn&#x27;t keep up with CPU speed. A cache miss will costs hundreds of nanoseconds. CPU speeds may have been doubling every 2 years or so, but memory access speeds have only been increasing by 10-20% or so.<p>In the 80s and 90s you just didn&#x27;t care as much about cache hits and misses. But those are the forefront of performance optimization strategies. &quot;Align your struct members&quot;,&quot;use structs of arrays instead of arrays of structs&quot;,&quot;think about cache lines and strides when you loop through your data arrays...&quot; etc.<p>And because CPU speeds go so much faster, memory access also stands out on performance charts. So GC languages and runtimes can still seems slow and sluggish for applications that don&#x27;t pay attention to memory.<p>2) Applications got more concurrent and servers are expected to handle a larger number of clients  &#x2F; connections &#x2F; requests. That means each one needs a context, so it needs memory. So memory is again at the forefront. Accessing it and its latency, GC pause times are important.<p>3) Mobile happened. Mobile devices have proliferated so the needs for fast, small footprint applications never went away. Even as there are serves witih terabytes of RAM around, there are even more little arm cores and then everyone talks about IoT. That means langauges&#x2F;runtimes which compile ahead of time will never be 100% displaced. Heck even on Android, ART (AoT copiling) is replacing JIT.