Why maintaining winit is hard
summary
winit maintenance is about grappling with platform quirks not abstractions: Windows and macOS start inner event loops during resize, iOS only offers a run that never returns, and WebAssembly requires returning from main and handing the closure to the browser. fixes include per-window threads, a single shared event-loop struct, closures passed into OS callbacks, process aborts to emulate exit, and a JS exception trick to unify wasm — each hack works in practice and frustrates clean API design.
AI-written summary · about
