I myself am waiting for 4K monitors in the 20"-24" size... My 7yr old 20" LCDs (1680x1050) are still doing well, and looking at replacements means about the only thing to look forward to would be an IPS panel (as my current ones are TNs). The resolution hasn't changed, or gone backwards as far as I'm concerned in this size range, unless you want to spend $$$.... The other thing I'm waiting for a true 10bit panels to come down in the price. (HP DreamColor monitors are expensive). While my monitors are only 6bit panels, from what I've read most on the market are still 6bit panels, unless you go high-end IPS, then you may actually get 8bit panels.
(In case you didn't undestand, I'm talking the actual displayed bits per colour channel, not the setting you set in your OS. Most TN panels are only capable of displaying 6bit colour channels (so the 24bit colour / 3 channels = 8bits per channel), is then dithered to 6bits per channel by the circuitry in the monitor). DVI/HDMI natively support 8bit per channel, and DisplayPort supports 10bit per channel. nVidia propriety drivers on Linux/BSD/Solaris have working 10bit colour channel support (and have for the last 4-5 years), but since most monitors don't support it most people don't realise it... IIRC, I believe Windows 7 has basic 10bit per channel support, but only a few applications support it correctly...
Operating systems are bad about supporting them as far as font scaling and the like (or at least communicating that they can do that stuff).
Actually, any GTK/QT based application is DPI aware and can scale correctly to any set DPI. (Gnome2/KDE exposed this to the user, Gnome3 hides some of the details). Xorg 7, also correctly gets the monitor EDID information which does include DPI for the monitor... It's because the GTK/QT toolkits don't work with pixels (unlike the Win32 GDI API, which is pixel based), and instead uses forms and packing guidelines for layout. Since the Win32 GDI API is pixel based, the application developers didn't/couldn't program DPI aware (and this is where a lot of previous Windows developers struggle with getting into Android development, as the Android UI API is DPI aware), so Windows users are stuck with a shitty UI that doesn't scale correctly (in all applications)... Also note: KDE and Gnome (and most other UNIX DEs) can use SVG based icons, and don't rely on fixed sized icons like Windows, so when they scale based on DPI, they actually look correct...