Direct Win32 API, weird-shaped windows, and why they mostly disappeared

Original Article ↗ Hacker News Discussion ↗

Weirdly shaped, heavily “skinned” Windows apps from the Win32 era evoke nostalgia but are widely seen as usability and accessibility failures that don’t scale to modern needs. Commenters contrast the fine-grained control and identity those native APIs allowed with today’s Electron and webview-based apps, which often feel bloated and inconsistent while still ignoring platform conventions. Underneath the aesthetics debate is a broader concern about Microsoft’s fragmented GUI strategy, cost-cutting pressures that favor flat, generic design, and the trade-off between creative interfaces and maintainable, accessible software.

Perception of the article & nostalgia

  • Several readers felt the writing style sounded machine-generated, though some still found it entertaining and evocative of past Win32 hacking.
  • The piece triggered nostalgia for 90s/2000s Win32 coding, Winamp-style skins, warez/keygen UIs, and old media players and chat clients with strong visual identity.
  • Others found it ranty and dismissed it early, especially where it seemed technically imprecise.

Weird‑shaped windows: identity vs usability

  • One camp celebrates odd shapes and custom skins as fun, expressive, and part of “making computers cool again,” especially for games, desktop pets, and toy apps.
  • The opposing camp stresses usability and accessibility: nonstandard shapes and custom widgets usually ignore platform conventions, break assistive tech, and waste screen space.
  • Many recall past “hall of shame” UIs, skeuomorphic excess, and hardware vendor bloatware as evidence that identity-over-usability goes badly.
  • Some argue both should be possible, but users—not developers—should ultimately control appearance.

Win32, message loops, and control

  • Multiple comments correct or refine the article’s take on Win32 control: the main loop is an event/message loop that the app owns via GetMessage/TranslateMessage/DispatchMessage.
  • Developers can subclass windows, delegate to DefWindowProc, use WM_NCHITTEST, hooks, or even detour low-level DLL calls to customize behavior.
  • Truly custom theming can expose awkward edge cases (e.g., scrollbars repainting in default colors, MessageBox reimplementation, version fragility).

Modern frameworks, Electron, and platform guidelines

  • Many complain that Electron/webview apps are heavy, inconsistent with OS UX, and often ignore accessibility and system theming.
  • Others prefer cross‑platform apps that look identical everywhere, valuing app‑specific consistency over platform idioms.
  • There’s broad criticism that major OS vendors themselves no longer follow their own HIGs, so “platform guidelines” feel less meaningful.

Performance, memory, and system evolution

  • Thread debates RAM usage: “unused memory is wasted” vs lived experience of systems freezing near 90% usage.
  • Comparisons of classic lightweight Win32 apps (old Notepad, EDIT.EXE) to modern versions and Electron-based tools (e.g., Slack) highlight large memory growth.
  • Some tie the decline of skeuomorphism and ornate UI to cost-cutting, rapid iteration, HiDPI complexity, and modern compositing (full backing stores for windows).