Loading...
Loading...
A pair of writeups revisits the era when Windows desktop apps routinely used direct Win32 API calls to build heavily skinned, non-rectangular “weird-shaped” windows for branding and novelty. By manipulating regions and messages (e.g., SetWindowRgn-style techniques), developers could create true ellipse or bitmap-shaped UIs without larger frameworks. The trend largely disappeared as Windows evolved: compositing and window manager changes, accessibility expectations, higher maintenance costs, and the industry’s shift toward standardized UI frameworks and, later, web-based cross-platform stacks like Electron and React. The coverage highlights a tradeoff between bespoke OS-level craft and today’s consistency and portability.
Windows apps once used the native Win32 API to create distinctive, non-rectangular, resource-efficient interfaces, but that era has largely vanished as developers favor web-based frameworks like Electron, React and Tauri. The author argues modern apps are bloated—example: a web-wrapped Notepad using ~50 MB versus a 1.8 MB Win32 C version—and lose the fine-grained control that enabled skins, irregular window shapes, and highly optimized desktop utilities on Windows XP-era software. This shift matters because it affects performance, memory use, developer skillsets, and the visual diversity of desktop software; it reflects broader trends toward cross-platform, web-centric development at the expense of native tooling and UX variety. The piece is a critique and nostalgia for native Win32 programming.
Windows once encouraged highly distinctive, non-rectangular desktop apps built directly on the Win32 API; modern apps, by contrast, mostly use web wrappers like Electron, React, and Tauri that prioritize cross-platform convenience over resource efficiency and UI identity. The article recounts how Win32 programming uses a message loop and window regions (HRGN) so developers can make true shaped windows — ellipses, bitmap-shaped interfaces, or animated mascots — by calling APIs like CreateEllipticRgn and SetWindowRgn. It argues the loss of that low-level craft led to homogenized, bloated apps but shows a small GitHub repo with examples to remind developers that direct Win32 control still enables unique, lightweight desktop experiences.
A Substack piece explored why early Windows applications used the Win32 API to create non-rectangular, heavily skinned windows and why those designs mostly vanished. It explains that developers used direct Win32 calls to shape windows for branding and identity, bypassing standard UI frameworks and controls. Over time, platform evolution, accessibility concerns, compositing/windowing changes, maintainability, and the rise of consistent UI frameworks and cross-platform toolkits made those custom-shaped windows impractical. The article matters because it shows how platform constraints and developer tooling shape interface innovation, and why modern GUI design favors consistency, accessibility, and easier maintenance over bespoke visual identity. Hacker News commenters noted some AI-like prose in the piece.
Windows apps once embraced highly customized, non-rectangular interfaces because developers wrote directly against the Win32 API; modern desktop software has largely abandoned that approach in favor of web-based frameworks (Electron, React, Tauri) that prioritize cross-platform convenience over tight resource control and unique UI identity. The article explains how Win32 message-driven programming and APIs like CreateEllipticRgn and SetWindowRgn let developers make true weird-shaped windows (ellipses, bitmap-shaped windows, animated mascots) without heavyweight frameworks. It argues this craft faded as fewer developers program at the OS level and as the web stack’s memory and bloat tradeoffs became acceptable. The piece includes a GitHub repo with Win32 examples to demonstrate these techniques.