Ask HN: Will programmers write more efficient code during the memory shortage?
Rising RAM prices driven largely by AI workloads have prompted debate over whether software will actually become more memory‑efficient. Many argue it won’t: developer time is still cheaper than deep optimization, end‑user devices and browsers absorb most bloat, and incentives favor shipping features quickly, often using heavyweight stacks like Electron and modern web frameworks. Others note that constrained environments—hyperscale data centers, mobile platforms, embedded systems and some game consoles—already optimize aggressively, and that better tools and LLMs might make targeted efficiency improvements more practical where there is a clear business benefit.
Overall sentiment
- Majority view: programmers will not significantly change behavior; memory will remain cheap enough relative to engineering time.
- Some expect at best a “freeze” in bloat, not a reversal.
- A minority report local efforts where memory optimization is now a company-level goal.
Incentives and economics
- Engineering time is seen as more expensive than extra RAM or cloud bills.
- Businesses tend to prioritize features, AI initiatives, and time‑to‑market over optimization.
- On servers, memory efficiency can directly reduce infrastructure costs, but only if savings exceed the cost and risk of optimization.
- For consumer SaaS, many expect price increases rather than deep engineering work.
Client vs server
- Client‑side memory is treated as “free” to developers; users mostly blame their hardware/OS, not individual apps.
- Server‑side memory is more likely to be tuned, but often via “stop doing obviously stupid stuff” rather than advanced algorithms.
- Some argue OS‑level tricks (compression, swapping) will be used rather than app‑level fixes.
Web, Electron, and framework bloat
- Many blame web stacks, SPAs, and Electron (“shipping a browser for each app”) for disproportionate RAM use.
- Others note that GUIs, ads, tracking, and large dependency trees are the real culprits, not core algorithms.
- Some optimism around alternatives (Rust, native, Tauri, mobile-style stacks), but skepticism about mass rewrites.
LLMs and languages
- Several expect LLMs to help rewrite Python/JS into Go/Rust and assist micro‑optimizations.
- Others worry LLM‑generated code may be more careless or unsafe unless guided by skilled engineers.
Games and constrained platforms
- Consoles, mobile, embedded, and scientific/grid computing already enforce strict RAM budgets; those ecosystems will keep optimizing.
- Desktop/PC games may adjust asset sizes and streaming strategies, but code complexity is less of the memory driver than high‑fidelity content.
Culture, skills, and education
- Repeated claims that many modern developers don’t understand low‑level memory, pointers, or performance trade‑offs.
- Some nostalgia for eras where software simply wouldn’t run without tight memory discipline.
- Several suggest real change would require metrics, promotions, and platform rules explicitly tied to efficiency.