HackerTube.dev

Windows 7 GUI slowness

VooD · 22.2K views · 2009-08-03 · 3:15

Open on YouTube ↗

If playback is restricted in your region, try opening the original video. Use Mark watched to add it to your marked videos.

Overview

A short demo showing slow 2D drawing in the Windows 7 GUI compared with XP. It attributes the slowdown to the display driver model lacking hardware accelerated GDI.

On Hacker News

Used as the reference example when people argue Windows UI responsiveness regressed after XP.

Recommended by 1 HN people across 1 months · HN mentions 2011–2025

Topics

Search by tags

What people said

kasabali · 2023-07 · Recommendation

Here's a more honest and direct introduction than Microsoft itself could wrote: [LINK] Especially follow the YouTube links demonstrating the problem: [VIDEO] [LINK]

Read the original HN comment ↗
ndiddy · 2025-10 · Reference

I remember when 7 came out and people complained about how the UI was less responsive than XP! Example: [VIDEO] I guess Windows UI responsiveness has just been steadily declining since the early 2000s.

Read the original HN comment ↗
StillBored · 2020-07 · Reference

While you might be slightly right, my experience tuning windows machines leads me to believe your missing the mark. I'm going to say the three largest contributions to general desktop lag are: Animations and intentional delays. It can't be said, how much faster a machine feels when something like MenuShowDelay is decreased to 0, or the piles of animations are sped up. Too many layers between the application draw commands and the actual display. All this compositing, vsync, and minimal 2d acceleration creates a low level persistent lag. Disabling aero on a win7 machine does wonders to its responsiveness. But even then pre-vista much of the win32 GDI/drawing API was basically implemented in hardware on the GPU. If you get an old 2d win32 API benchmark, you will notice that modern machines don't tend to fare well in raw API call performance. 30 seconds poking around on youtube, should find you a bunch of comparisons like this [VIDEO] . Keep in mind that even in 2020 pretty much every application on the machine is still relying on GDI (same as linux apps relying on xlib). Input+processing lag, USB is polling with a fairly slow poll interval rate (think a hundred or so ms). Combined with the fact that the keystrokes/events then end up queued/scheduled through multiple subsystems before eventually finding their way to the correct window, and then having to again reschedule and get the application to retrieve and process it via GetMessage()/etc. Basically, this is more a function of

Read the original HN comment ↗

Sources

Video by VooD, played through YouTube.

Data and selection notes

HN summaries and labels may contain AI errors. HN dates refer to discussions, not video publication.

HN Library: HackerTube export (2026-10-31) and open-index/hacker-news. Upstream summaries and classifications may contain AI errors.

Views, duration and playback status refresh separately from the published catalog. When an update fails, existing data remains visible.

Selection checks
  • SaaS & AI candidates: Topic keywords do not match
  • Editor-approved picks: Editorial review is required

Rule matches identify candidates. They do not guarantee video quality or financial results.

About the library and its sources