Legacy Systems on MacWorkshttps://macworks.dev/tags/legacy-systems/Recent content in Legacy Systems on MacWorksHugoen2026-05-02https://macworks.dev/docs/archives/hackernews/hackernews-2026-05-02/Mon, 01 Jan 0001 00:00:00 +0000https://macworks.dev/docs/archives/hackernews/hackernews-2026-05-02/<h1 id="hacker-news--2026-05-02">Hacker News — 2026-05-02<a class="anchor" href="#hacker-news--2026-05-02">#</a></h1> <h2 id="top-story">Top Story<a class="anchor" href="#top-story">#</a></h2> <p><strong><a href="https://evilgeniuslabs.ca/blog/winforms-still-ships-in-visual-studio-2026">Visual Studio 2026 still ships the form designer Alan Cooper drew in 1987</a></strong> It is prime HN material: a deep architectural dive into why Microsoft&rsquo;s endless attempts to kill WinForms in favor of WPF, Silverlight, UWP, and MAUI all ultimately failed. The reality is that WinForms survived because it is a thin, strongly-typed wrapper over the Win32 API, specifically <code>USER32</code>—the most aggressively backward-compatible API surface Microsoft owns. It is a great reminder that &ldquo;legacy&rdquo; often just means &ldquo;done,&rdquo; and that line-of-business applications care more about shipping a working form than adopting the newest web-tech UI.</p>