Slashdot Mirror
Why Are We Losing Vertical Pixels?
An anonymous reader writes "Switching from 1600x1200 to wide 1680x1050 to HD 1600x900, we are losing more and more vertical space, thus it is becoming less and less simple to read a full A4 page or a web page or a function call. What's the solution for retaining the screen height we need to be productive?"
Buy a different monitor or buy two or turn one sideways.
The linked article was talking about laptop screens, where that's not really an option. I could see some humorous results if you tried. The solution is just as simple: Develop on an external monitor (optionally rotated 90 degrees).
Yea, I tried that but my desk isn't long enough for my legs.
stop upgrading to shittier technology.
check out my comic: Essential Tremors
> You get what you pay for.
Excellent. I've got some real estate to sell you...
Warning: this article may contain humor, sarcasm, parody, and perhaps even irony. Read at your own risk.
Have you ever tried to use a 16:9 monitor turned sideways? It's ridiculous. The viewing angle on the vertical (now, the horizontal) part of the monitor is terrible so you have to be sitting exactly in front of it or you can't see it. This is no good if you have 2 monitors. The monitor is so tall that your focus on the top and bottom parts of the monitor are different.
The trouble with turning an LCD monitor sideways is that text looks terrible. I use a widescreen monitor rotated for code visibility purposes. The excess cruft of IDE subwindows is much less disruptive. However, text (and even code) is significantly more readable (and less painful) on the smaller, non-rotated monitor.
Windows doesn't seem to properly do sub-pixel rendering on a rotated monitor -- all of the ClearType profiles are based on the configuration of subpixels in a normally-oriented monitor. Moreover, the settings don't seem to be on a per-monitor basis, which means that I would get to choose to have one of my two monitors look terrible and one be legible. Does anyone know of a ClearType (or similar) tool for Windows which properly adjusts to rotated screens? (I'm off to Google it... maybe it's easier to find this year?)
Then there's the issue of viewing angles -- most LCDs have a wide horizontal viewing range, but a narrow vertical viewing angle range. Rotating the monitor flips that. (It's not as big of a deal as you'd think, in that I sit in generally the same place, but it makes it harder to read stuff there if someone is sitting next to me.)
I totally agree. I tried "rotated" for a while and performance and overall experience was bad. The colors looked slightly different and unbalanced. My guess is that viewing angles are optimized for using the monitor in "normal" (un-rotated) mode, and the average viewing angle may not be normal to the screen surface. So when you rotate the thing it all gets messed up. There are also more subtle issues: how to handle sub-pixel anti-aliasing (like in Windows ClearType) when one monitor is rotated and the other one is not?
I'm not sure what you're on, but reading narrow columns is way faster than reading wide lines. That's why newspapers have columns. One of the many deficiencies of CSS is that it's practically impossible to a newspaper-like layout which works at any screen size (adapting the number of columns as needed).
Finally! A year of moderation! Ready for 2019?
You're not losing pixels, you're just throwing numbers out there without actually knowing what you're talking about. 1600x1200 is UXGA. 1650x1080 is WSXGA+, which is the widescreen variant of SXGA+ (1400x1050). If you want widescreen based on the 1600x1200 resolution, buy a WUXGA monitor(1920x1200). Pretty simple, really. You only "lose" pixels if you don't research the monitor you are purchasing.
Try a Thinkpad, they have 15" ones that go to 1920x1080.
There is no significant difference in latency or duration for vertical vs. horizontal saccades (eg: see ), and you're dead wrong about reading speed: In English, the optimal column width for fast reading is somewhere between 50 and 100 characters per line, depending on exact circumstances.
However, there are two other relevant facts: 1) The lower visual hemifield has a larger cortical representation than the upper visual hemifield, and shows modest improvements in visual performance (this is unsurprising, since our hands/tools/ground near us is usually in our lower hemifield) and 2) We can move our head side-to-side more rapidly, and with a larger range of motion than we can up and down, which changes some saccade distributions.
Irregardless of the mechanics of the situation, reading is a highly trained activity, and direction of reading is not universal. Chinese, for instance, can be read top-to-bottom, or with either horizontal possibility as the initial direction, with the reader cued by slightly differing strokes and punctuation . I'm not aware of any bottom-to-top sequential reading in any culture, which is probably due to the above mentioned processing differences. However, there are also mixed reading sequences that use multiple horizontal and vertical elements in a single block, like Mayan hieroglyphs (2x2 blocks LR->TB within block, blocks are read TB->LR ) or the Korean Hangul system (variety of block sizes, read TB->RL). Arguably, the latter systems are most efficient in terms of leveraging the early geometry of the visual system (log-polar, with resolution dropping exponentially with distance from the fovea.