I don't know if a completely square monitor would be as well received as something at least slightly rectangular - 1920x1440 (4:3) might be a good compromise.
I don't know if a completely square monitor would be as well received as something at least slightly rectangular - 1920x1440 (4:3) might be a good compromise.
When I code, horizontal space is never at a premium. It's always vertical space I'm short on.
Pulling out my T42p retro laptop, with its 4:3 screen, always gives me the warm fuzzies. Love that aspect ratio.
This is incredibly useful to a whole load of office employees, who want to refer to two word docs, or 1 word doc and 1 PDF, etc. This is where widescreens shine (and 16:10 is even better than 16:9) and why I think they've excelled well in the workplace.
A 16:10 monitor rotated 90 degrees (what I have right now) is OK, but it wastes space at the top and bottom that the 4:3 monitor would be using to zoom the document more.
A horizontal 16:10 monitor with two PDF's, as you mention, is too small for me (at least with my current 24 inch monitors). Caring for the eyes is essential when you're looking at on-screen PDFs all the day. I would probably like that layout with a 30" monitor though... although maximizing windows in two monitors is still more comfortable than tiling in one big monitor.
If you're using Windows, here's a neat feature I went years without knowing: Windows key + left arrow arranges the window to occupy the left half of your monitor, and similarly with right arrow.
The last few places I've been have been strong supporters of dual monitors, so I might be in a bit of a thought bubble on that, but also because monitors have gotten dirt cheap so why not. You can get dual IPS for the price of a fancy office chair.
I’m seriously considering buying an LG 34UM95 monitor¹ for precisely this reason. It’s so wide (34" screen, 21:9 aspect ratio, 3440x1440 resolution) that I could sensibly divide the screen into 3-4 full-height columns with different source files open in each for development work.
Currently I have a decent Dell 30" as my main screen, but at 2560x1600 resolution I wind up using it with a 2x2 split for coding, which roughly halves the number of lines I can see at once in a long file.
I’m a little sceptical about trying a 1920x1920 screen at that physical size for similar work, simply because I’d worry about what prolonged use would do to my neck with that much vertical movement being needed all the time.
tl;dr: Vertical: Mostly eye movement. Horizontal: Lots of neck movement.
Given proper resources, I'd consider getting one. Just wanted to share my funny anecdote that it's so large, I rolled back and forth to take advantage of it all :)
However, from my typical centered vantage point, windows near the corners appeared skewed.
Presumably this is the advantage of the new curved screen version¹, though so far it’s considerably more expensive and it looks like at least here in the UK no-one has it available for immediate purchase.
They call these 16:9 displays widescreen. I call them shallowscreen: they are just don't have th evertical space for work. Why are my work tools made with screen form factors that are only suitable for watching movies?
And yes, I love my T43, which has a lovely display and keyboard even though it is almost 10 years old. Alas, it is just underpowered today.
Last time I completely rebuilt my home setup I got monitors that can be rotated into portrait. I've not used the facility nearly as much as I thought I would, but then again I've not done much development since so that might be why.
Having one portrait and one landscape seems to be idea for web development: portrait for coding and landscape for output (as that is what the user's will likely have) & the things that don't fit properly in 1080 pixels wide.
You don't want to large a monitor in portrait for coding though: you'll be looking down a lot (or up+down if you sit with your head centred) which might be quite bad for posture. Beyond a certain size you are probably better off with a large monitor and some UI hack to artificially split it into columns.
It certainly is. My browser is never even that wide now, and the only thing I ever run full screen is games.
4:3 is about right for a laptop since you can't make them too "tall" or they'll become difficult to handle, much like books.
It seems to me that a 16:9 monitor is exactly what you need -- rotated vertically. Get one that pivots!
This sounds really weird to me. I absolutely relish the ability to have an editor and terminal side by side without either of them feeling "squeezed up". If you're using an IDE you can also get a lot more space for actual code even with those annoying side areas that IDEs tend to have.
I recently upgrade to a 5k imac... and it's an absurd amount of space. I don't see the point in griping about aspect ratio when it's merely size and density that we really want.
But on a large desktop display, I end up with lots more windows at any one time, including lots of small windows that stay around and in one place for a long time: things like notes, feeds, things to come back to, etc. And, in that large space, I can size each window as large as I want, so I much more often can use a natural-feeling aspect ratio for its content. In other words, large displays are the only ones for me in which a "desktop metaphor" GUI actually feels and functions like a desktop. So, on a large display (aside from games/movies), I don't care too much about aspect ratio, I'll fill up the edges of whatever space I've got.
My current fave monitor at home is my ca2008 Dell 2405 with all it's 1920x1200 glory. The Pixel is second, but a distant second because the screen is so small that if you actually use the full resolution you can't read a darn thing.
What's happening in the sky or on the ceiling isn't particularly useful to us, and as long as we have reasonably sure footing, the same is true of the ground or floor. We spend our days interacting with things mostly in the horizontal visual plane. Things that we approach or that approach us mostly move in this plane as well.
[1] There were a few famous experiments a few decades ago showing that what we see as we grow up affects the development of the visual system: https://computervisionblog.wordpress.com/2013/06/01/cats-and...
Unfortunately, OSes and other software tend to mess this up: in particular, the fact that those handy fullscreen commands actually fill the screen with the selected window or picture or video or whatever is no longer good news if some or all of the edges of your screen are far enough away from the comfortable centre area of your vision (see http://blog.codinghorror.com/the-large-display-paradox/ ). This was appropriate behaviour in the past, when both pixels and screen inches were limited and expensive and so it was safe to assume that the whole of the screen was well within the user's central viewing area—and in fact was probably covering much less of that central area than was at all ideal. Nowadays the user should be able to define a central fullscreen area that (possibly) doesn't take up the whole screen: then (by default etc.) fullscreened items should be expanded to the limits of the "fullscreen" area and no more. The rest of the screen can be filled with other information: maybe the other open windows pushed to the side in an OS X Exposé-like manner, or things like image metadata for a viewed image. The brightness of the outer area should be subdued to prevent it from distracting from the central image. (A practical use for whizzy translucency effects!). The information out in the "gutter" will be glanceable, but won't feel like it's impinging on your view of the fullscreened item (if it does, you didn't make the fullscreen area large enough).
16 / 9 = 1.77
2560 / 1140 = 2.25
It's closer to today's CinemaScope: http://en.wikipedia.org/wiki/CinemaScope "today it generally refers to any 2.35:1, 2.39:1, or 2.40:1"
resolution size width x height ppi
2560x1440 25" 21.8" x 12.3" 117
1920x1200 24" 20.4" x 12.7" 94
1920x1080 24" 20.9" x 11.8" 92