hn.today

Why Windows 11 still ships with Windows 95's memory manager hidden inside it

windowslatest.com107 points74 comments
Screenshot of Why Windows 11 still ships with Windows 95's memory manager hidden inside it

Commenters discussed claims that Windows 11 still contains legacy memory-manager code tracing back to Windows 95 (and even Windows 3.1) as a compatibility measure. Several people (abanana, philipallstar) pushed back on the idea that the SimCity fix was a one-off, arguing Microsoft systematically engineered backward-compatibility hooks through Windows 95 and XP to keep old 16‑bit software working. Others (LASR, Barrin92) celebrated that ability to run decades‑old apps as a strength; critics of the article itself (jonathanlydall, immibis2, pishpash) labeled the writeup weak, SEO-driven, or AI‑rehashed, and one commenter (Dwedit) complained about an irrelevant screenshot choice.

Opinion divided on whether such compatibility is inherently good. Blikkentrekker defended long-term compatibility as essential, citing Python 3/Wayland disruption and legacy COBOL on z/OS, while others raised technical points about where allocators belong: jeffbee argued allocators should be linked into applications, pcwalton and bigfishrunning noted userland DLLs and MMU address spaces handle allocations, and hyperhello and bboreham referenced historical debugging tools like Purify. Practical notes included links to NTVDM/WINE projects (ranger_danger) and mixed views on where to find support for legacy issues (expedition32 vs Spivak).

Read on windowslatest.com74 comments on Hacker News

Summary generated by AI from the linked article. hn.today is not affiliated with Hacker News or Y Combinator.

More in Other

The daily digest

Today's best Hacker News stories, summarized and screenshotted, one email a day.