Widescreen laptops are dumb
theverge.com
theverge.com
Tabs are at least three decades old now, and they weren't originally restricted to just one edge of the window:
>Tab (GUI):
https://en.wikipedia.org/wiki/Tab_(GUI)
>The WordVision DOS word processor for the IBM PC in 1982 was perhaps the first commercially available product with a tabbed interface. PC Magazine in 1994 wrote that it "has served as a free R&D department for the software business—its bones picked over for a decade by programmers looking for so-called new ideas". The NeWS version of UniPress's Gosling Emacs text editor was another early product, with multiple tabbed windows in 1988. It was used to develop an authoring tool for the Ben Shneiderman's HyperTIES browser (the NeWS workstation version of The Interactive Encyclopedia System), in 1988. HyperTIES also supported pie menus for managing windows and browsing hypermedia documents with PostScript applets. Don Hopkins developed and released several versions of tabbed window frames for the NeWS window system as free software, which the window manager applied to all NeWS applications, and enabled users to drag the tabs around to any edge of the window.
Notice the layout of the overlapping Emacs windows with tabs sticking out of their right edge: since text is much wider than it is tall, you can stack up a lot more tabbed windows with tabs on their left or right side, and still read their labels.
>HCIL Demo - HyperTIES Authoring with UniPress Emacs on NeWS:
https://www.youtube.com/watch?v=hhmU2B79EDU
>Demo of UniPress Emacs based HyperTIES authoring tool, by Don Hopkins, at the University of Maryland Human Computer Interaction Lab.
Notice how you can drag the tabs of these NeWS windows to any edge or proportion of the height or width, and use the tab as a proxy for the window by popping up a window management pie menu on it, even if the rest of the window is covered:
>NeWS Tab Window Demo:
https://www.youtube.com/watch?v=tMcmQk-q0k4
>Demo of the Pie Menu Tab Window Manager for The NeWS Toolkit 2.0. Developed and demonstrated by Don Hopkins.
Notice how the tabbed windows can be stuck on the visual PostScript stack like a short order chef's "spike". The tabs enable "direct stack manipulation": and they are constrained (by "snap dragging") to slide up and down on the stack (rearranging the order of the items on the PostScript stack), and can be pulled far enough away that they "pop" off the stack, or dragged back onto the stack so they snap into place, and you can directly drop them into any depth of the stack.
>PSIBER Space Deck Demo:
https://www.youtube.com/watch?v=iuC_DDgQmsM
>Demo of the NeWS PSIBER Space Deck. Research performed under the direction of Mark Weiser and Ben Shneiderman. Developed and documented thanks to the support of John Gilmore and Julia Menapace. Developed and demonstrated by Don Hopkins. Described in "The Shape of PSIBER Space: PostScript Interactive Bug Eradication Routines".
>The Shape of PSIBER Space - October 1989. PostScript Interactive Bug Eradication Routines.
http://www.donhopkins.com/drupal/node/97
>There is a text window onto a NeWS process, a PostScript interpreter with which you can interact (as with an "executive"). PostScript is a stack based language, so the window has a spike sticking up out of it, representing the process's operand stack. Objects on the process's stack are displayed in windows with their tabs pinned on the spike. (See figure 1) You can feed PostScript expressions to the interpreter by typing them with the keyboard, or pointing and clicking at them with the mouse, and the stack display will be dynamically updated to show the results.
>Objects on the PSIBER Space Deck appear in overlapping windows, with labeled tabs sticking out of them. Each object has a label, denoting its type and value, i.e. "integer 42". Each window tab shows the type of the object directly contained in the window. Objects nested within other objects have their type displayed to the left of their value. The labels of executable objects are displayed in italics. [...]
>Tab Windows
>The objects on the deck are displayed in windows with labeled tabs sticking out of them, showing the data type of the object. You can move an object around by grabbing its tab with the mouse and dragging it. You can perform direct stack manipulation, pushing it onto stack by dragging its tab onto the spike, and changing its place on the stack by dragging it up and down the spike. It implements a mutant form of "Snap-dragging", that constrains non-vertical movement when an object is snapped onto the stack, but allows you to pop it off by pulling it far enough away or lifting it off the top. [Bier, Snap-dragging] The menu that pops up over the tab lets you do things to the whole window, like changing view characteristics, moving the tab around, repainting or recomputing the layout, and printing the view.
>Designing to Facilitate Browsing: A Look Back at the Hyperties Workstation Browser. By Ben Shneiderman, Catherine Plaisant, Rodrigo Botafogo, Don Hopkins, William Weiland.
http://www.donhopkins.com/drupal/node/102
>Since storyboards are text files, they can be created and edited in any text editor as well as be manipulated by UNIX facilities (spelling checkers, sort, grep, etc...). On our SUN version Unipress Emacs provides a multiple windows, menus and programming environment to author a database. Graphics tools are launched from Emacs to create or edit the graphic components and target tools are available to mark the shape of each selectable graphic element. The authoring tool checks the links and verifies the syntax of the article markup. It also allows the author to preview the database by easily following links from Emacs buffer to buffer. Author and browser can also be run concurrently for final editing. [...]
>The more recent NeWS version of Hyperties on the SUN workstation uses two large windows that partition the screen vertically. Each window can have links and users can decide whether to put the destination article on top of the current window or on the other window. The pie menus made it rapid and easy to permit such a selection. When users click on a selectable target a pie menu appears (Figure 1) and allows users to specify in which window the destination article should be displayed (practically users merely click then move the mouse in direction of the desire window) . This strategy is easy to explain to visitors and satisfying to use. An early pilot test with four subjects was run, but the appeal of this strategy is very strong and we have not conducted more rigorous usability tests.
>In the author tool, we employ a more elaborate window strategy to manage the 15-25 articles that an author may want to keep close at hand. We assume that authors on the SUN/Hyperties will be quite knowledgeable in UNIX and Emacs and therefore would be eager to have a richer set of window management features, even if the perceptual, cognitive, and motor load were greater. Tab windows have their title bars extending to the right of the window, instead of at the top. When even 15 or 20 windows are open, the tabs may still all be visible for reference or selection, even thought the contents of the windows are obscured. This is a convenient strategy for many authoring tasks, and it may be effective in other applications as well.
https://upload.wikimedia.org/wikipedia/en/2/29/HyperTIESAuth...
Unfortunately most of today's "cargo cult" imitative user interface designs have all "standardized" on the idea that the menu bars all belong at the top of the screen and nowhere else, menus items should layout vertically downward and no other directions, tabs should be rigidly attacked to the top edge and no other edge, and the user can't move them around. But there's no reason it has to be that way.
Designers of many sites I have to use daily seem to assume I’d never want to see two windows at once, let alone rearrange my UI or use non-widescreen devices. The responsive sites can be even worse too since they’ll snap into a mobile layout at anything less than 1000px wide or so and then increase all of the margins and icon sizes for touch accuracy purposes. It looks extremely silly and wastes even more space than these layers of toolbars hanging around the edge of a browser.
That's been a problem for roughly twenty years now. Way back in the 1990s (on a 4:3 CRT, natch) I started out with half the screen dedicated to my browser and the other half left free for other things (back in those days it was normal to have many windows open at once on a Mac screen — weird how we have so many more pixels now, but typically just have one thing on the screen at a time!).
Eventually I had to stop doing that, because so many sites assumed that I'd have the browser opened full-screen. At the time, I believed that to have originally been a Windows-ism, but I don't know anymore if that was really the case.
Even though I love my tiling WM, I do kinda miss the days when I'd have multiple windows open. Now, I have a second, portrait-mode, monitory — but I only have code on it, and leave my browser on the landscape-mode screen.
Sure, the visual treatment of maximized windows felt "more natural" on Windows, but the Mac's #$@&! global menu bar often made moving between multiple non-maximized apps more annoying (especially on a large display).
Really, a small resolution laptop is vastly less common than mobile on most websites. Looking ugly but working for group A is much better than not working for larger group B.
Yea, iPhone X should say 812px width landscape etc, but that's not necessarily happening.
This is how http://clientkit.io/ looks for me:
We’re using the latest version on http://leanin.org
Since the 90s, my first test with any new design was to resize the browser and see how the page reacts. Most of the time they failed.
This is due to the nature of humans' visuospatial limitations. We're largely 2d animals in our movement: front/back & left/right, not so much up down. This is different from animals like birds and fish who constantly have to navigate all 3 dimensions to catch prey and avoid death.
We aren't ignorant of vertical space, but horizontal space is much more well attended to by the human brain, spatially and visually. (Video game designers encounter this problem in getting players to look up.)
Vertical screens for the masses started with mobile, because constraints of the hand matter more than the biases of vision in that case.
Of course as desktop screens become giant, lateral vs vertical space becomes a less important distinction, but understanding why "widescreen" came about over "square" is important. Of course, this all varies by task, but I imagine this is a big reason why 16:9 came about.
When it comes to scanning for unexpected information, you may be right. A high aspect ratio might be better suited for gaming, at least with games where a significant element is scanning the screen for information and responding to it quickly.
One more data point to throw in is that according to Wikipedia, the human field of view is approximately 1.5:1. That suggests to me that 1.5:1 is a good aspect ratio for a general-purpose display. https://en.wikipedia.org/wiki/Human_eye#Field_of_view
edit: I just realized a 3:2 screen is basically two 1.5:1 "areas". There are some laptops that have a 3:2 screen mentioned in other places in this thread.
I do wish I had a better way of splitting content into readable newspaper style columns, though. Modern web design is pretty antagonistic toward this end. There was a MacOS app that used to do this[0], but it hasn't been updated in years and there isn't an alternative for windows.
(Though best supported by Firefox and Edge, with interesting bugs in Chrome and Safari I've seen.)
With one major flaw in that -ms-scroll-translation still hasn't made it out of being just an IE 10 suggestion (that Edge still supports and no one else) and into the specs and is a pain to polyfill, but a relatively key ergonomic need: https://msdn.microsoft.com/en-us/library/hh973361(v=vs.85).a...
Windows 8 tried to encourage horizontal scrolling, multi-column design in applications and websites, so Microsoft put some good work into the ergonomics of it, and I appreciated they tried and am still somewhat sad they failed.
(I'm proud that my blog uses a multi-column layout for text at wide widths, but given it is my blog I can do weird design craziness like that that amuses/interests me and not worry about confusing potential visitors.)
I don't find 3:2 to be an especially good aspect ratio for fullscreen text. It's still either too wide or too short, but 3:4 is pretty good, so two columns on 3:2 is two pretty good text areas on a 12-15" diagonal screen. It's also one pretty good text area and some UI, ads, etc... on either side.
I should note that physical size is a major constraint here. On a laptop, I want a column of text to be about 4-6" (10-15cm) wide. A desktop screen that's usually farther away can be a bit wider, maybe 8-10" (20-25cm). Having those columns be very tall is fine. I've been using a 24" 9:16 display for having documentation up while coding lately.
The other one is internal real estate. Wide screens mean wider keyboards and larger batteries.
Edit: after posting I realized something was missing. I meant had they done this and increased the diagonal to say, 17 or more inches.
My favorite is the headers that mess up scrolling with the space key -- scroll down then immediately scroll up because the header is covering part of the content.
And don't even get me started on sites (looking at you Medium) that have both headers and footers...
Many of us never use our laptops (especially employer-owned ones) for full-screen video, or have no objection to the letterboxing and slightly smaller video size when we do.
"Nearly useless" seems like a ridiculous exaggeration to me. I have an iPad (4:3) used for little other than video, and love it.
It works (kinda) but I miss having the whole page at a view...
I don’t know why screens still care about optimizing video...I can’t remember the last time I watched something full screen when there’s picture-in-picture. As with other software, I want to do multiple things and not necessarily just sit and watch something.
For decades software has had a weird laziness when it comes to making things simply resizable. Ever seen a program pop up a list of 1000 choices that only shows about 4 of them, truncating half the names, with a useless miniature scrollbar and no ability to resize, on a gigantic screen?
The day I got the iPad 1, it was the coolest thing ever. It took just weeks for that to be gradually ruined by ridiculous decisions made in software (web sites that could no longer be pinch-zoomed trying to “help” me with a “mobile-optimized” interface, apps lazily zooming up from phone sizes and making terrible use of space, etc.). To this day I would never opt into a “pro” version of that experience; I simply can’t stand software that constantly wants to tell me how much space I have been rationed for each thing.
If you grew up in North America, the 4:3 ratio probably feels the most natural because it's closest to the standard 8.5"x11" Letter paper size that almost every sheet of paper you've dealt with in school is.
Also, the 21:9 (2,333) it's a lossy approximation to the silver ratio (2,414).
But probably nobody knows that 4:3 (1,333) it's a lossy approximation to the Córdoba ratio (1,306).
Yes, the most popular screen sizes approximate to the most beauty rectangle proportions.
* https://en.wikipedia.org/wiki/Golden_ratio
* https://en.wikipedia.org/wiki/Silver_ratio
* https://es.wikipedia.org/wiki/Rect%C3%A1ngulo_cordob%C3%A9s (Spanish)
(Though I've been keeping my main taskbar on the right hand side since XP and that was perfectly reasonable then even. These days, I tend to sandwich my Windows taskbars these days with it on the left on the left monitor and on the right on the right monitor.)
I also have an issue where if I've got multiple windows from a single app open in different virtual desktops, the only way to get to the other windows from the app is to click the dock icon - it can't be done via keyboard as far as I can tell. (And yes, it's infuriating.)
Then again my use of the dock is sporadic, mostly for accessing recent downloads.
This is not the fault of the hardware, it's the fault of the software. I want more screen space, and I'm not asking for a square laptop and I'm not wanting my screen any taller than it is.
Browsers should optimize for vertical space and let you reuse your horizontal space. Tree-style or vertical tabs are perfect for this. But for some reason, all browser vendors follow each other, don't build alternative options (or count on the community to do it if they even allow that), and presume they have got it right with tabs on the top. It's like browsers have become so hard to build and maintain by the big four that having more than one way to view things is disallowed or relegated to extensions. I've said it before, I want my browser like my IDE. I want to move and dock windows in a MDI, and I want to move around the web like a power user. Yet we're all subject to the lowest common denominator of users because, I suppose, maintaining more than one UI paradigm is too difficult and they've all settled on the best apparently.
This easily boils down to the fact that our language is horizontal, and we don't read rotated text very well.
It informs design decisions, creating horizontal tab bars, menu bars, navigations, etc.
Emacs with tabbed windows:
https://upload.wikimedia.org/wikipedia/en/2/29/HyperTIESAuth...
https://www.youtube.com/watch?v=hhmU2B79EDU
It sucks that "standard" tabs are always along the top edge: you can only fit a few of them, and their labels are clipped so you can't distinguish them, and you can't do anything about that. You should be able to move them to any edge and adjust them according to the task, tab count, label size, screen dimensions, and personal preferences.
Ideally, users should be able to choose which edge and how far along each edge to place the tab, adjust the tab's size and rotate its orientation, iconify and expand windows to and from their tabs, and easily group windows together by their tabs in rows or columns as desired (including docking inside other windows, or nesting tabs in 2D tree outlines using different edges and orientations at each level).
"Direct Manipulation" PostScript stack editing with tabbed windows:
http://www.donhopkins.com/drupal/node/97
Dragging tabs between different window edges:
Vivaldi has in the options (without any 3rd party add-on) a possibility to put your tab bar either on top, left, right, or bottom.
[0]: https://www.theverge.com/2012/6/5/3062470/toshiba-21-9-ultra...
Then again... even with that, I guess I agree with the OP. Even after turning on the sidebar, there's more horizontal space than I need. And I love screen real estate.
I long ago got used to black bars, and don't watch that much video on my laptop anyway. Usually when I do, I'm connected to an external monitor.
Sony also tried this with the VAIO P, in a smaller format with a 1600x768 screen.
As a router jockey, I use widescreen (laptops) for multiple terminal sessions, iterm2 with 4 or 6 80x40 cli windows.
People see the latter and think it is quite similar to 16:9 because the 16s are the same, and don't realize that this is not true. 16:10 is actually closer in form factor to 3:2 than 16:9.
But as a neighbor reply pointed out, it would probably be best to normalize to one. Do you want a 1.5 aspect ratio (3:2) or a 1.77 (16:9) one? Much easier to compare single numbers with each other.
Particularly for screens, which most people think of in terms of two dimensional surfaces, using simple fractions seems more obvious, and for ratios like 4:3 and 16:9, numbers are particularly useless because they can't be used to exactly describe the relationship.
Trickier on a laptop but can't someone design a 'convertible' with a rotate-able kickstand, so that a detachable typecover snaps into place regardless of whether the screen is in landscape or portrait?
Aspect ratios and orientation are moot if you have more real estate and pixels.
If you were to have something like a 55" curved 8K monitor and good eyesight (or glasses), aspect ratio would be less important to you, since that screen would cover most of your field of view while still providing you with high pixel density.
For many years (since I grab my first 16:9 screen), I used and suggested to others to put the taskbar on a lateral. Because It allow to display more text! You have a more wide screen and you can afford to lose a few of horizontal space better that losing a few of vertical space.
I once heard a rumor that they were doing widescreens because they were cheaper to manufacture... not sure how true that is...
I can only think of Japanese that may be written vertically.
For a long time, we suffered from what I'll call "The Great Laptop Display Regression of 2008". For many years, you simply could NOT buy a non-Apple laptop with more than 1080 pixels in the vertical direction. It didn't matter how big of a screen you got, and it didn't matter how much you were willing to pay for it. No one dared even give you the option.
I still have what I believe is one of the last great laptops with a 1920x1200 display. It's a 15 inch Core 2 Duo 2.66Ghz Dell with gigabit Ethernet from around 2008-2009. It's not my primary driver. It's used as a Plex Server running Windows 10.
I'll occasionally use it for browsing when I am working from home using my work laptop on the VPN.
I usually have a two monitor setup, but my next personal computer will be a 27 inch 5K iMac. I want to be able to use one monitor with an IDE on one half and the browser on the other half.
It is very often that I find myself debugging or reading code for the first time and need to dive into several layers of code. Having it all side by side helps tremendously.
YMMV
Switching between a laptop and multi-monitor setup was a bit comical for me despite trying it for a month. Even something as simple as alt-tab focusing a window that's not on the expected screen would slow me down.
It wasn't for me. And my productivity improved once I moved back to a single 26in monitor.
The super-wide is way too short, vertically, that I have no interest in using one.
I actually have two of those 30" displays on my desk. My approach is do to most of my work on the primary, and to shove some chat windows, log windows, etc, to the secondary. So I'm really using all of one display, and maybe half of the other. (Of course once displays get this big, the other half of the secondary display is too far from my field of view anyways.)
If anyone is interested, I use the VESA mount conversion kit from Apple and have the monitors mounted on the Amazon Basics monitor arms, which I highly recommend.
I've been using this setup for about 18 months now, and I really rate it. 1440x2560 is a very usable resolution. Very few problems with websites (I had regular minor issues when I had a 1200x1920 screen); tons of lines of code on screen; plenty wide enough for 2 side-by-side columns; I don't find it a problem to use 3 side-by-side columns (77 columns apiece) in Emacs with a small font; small desk footprint.
Full-height windows are sometimes a bit much, but for the main display I've found having one window or panel that's 2/3 the height and one that's 1/3 the height works very well. The 1/3 height area is still 1440x850 or so - plenty for a terminal, Emacs window, debugger output, that kind of thing.
As a bonus, 1/3 of the screen is a bit taller than 16:9, so good for videos, and 2/3 of the screen is about the right proportions for A4 PDFs. Considering it's just the not-very-good 16:9 turned on its side, I've found 9:16 to work remarkably well...
(With the proviso that the pixel count is almost certainly relevant, and I very likely would not feel as positive about 1080x1920...)
That may be a reflection on the cleanliness of our codebase though...
In my setup with Emacs, a 1600x1200 screen and 12px monospaced font, I have two 86 character wide windows side by side. To add another column without changing something else, I would need a 2400px wide screen.
I wouldn't object to a large 2:1 aspect screen on my desktop, but it makes for an unwieldy shape for a laptop.
I'm not at work right now, but from memory I get around 120 characters in each column without any sidebars.
I'm in the camp that finds 16:9 / 16:10 to be the wrong ratio for... everything. Maybe a giant high-DPI display would make it better. For now, having four windows arranged as though they were maximized on a 2x2 grid of 4:3-ish displays perfect suits how I like to work.
I really despise how the Xcode team thinks that iTunes was a good inspiration for a UI.
The Interface Hall of Shame: QuickTime 4.0 Player
http://hallofshame.gp.co.at/qtime.htm
Apple's long romance with skeuomorphism peaked with Bob Bishop's APPLE-VISION, and went downhill from there.
What is it about media player software in particular where everyone from the beginning had to have weird skeuomorphic UIs? Even the early examples I can think of (AppleCD Player, Creative's Windows 3.1 stuff, Winamp) all had to have non-native UIs. Preferably with a fake segmented VFD/LED display https://panic.com/extras/audionstory/popup-images/popup-appl... http://i.imgur.com/27tgh8S.png
edit: that Apple Vision demo is gorgeous! (hah)
I beg to differ. I have a UWQHD and love it for code. I can have 2 sets of code side by side (or a terminal) AND docs AND the website I'm working on, all visible without moving windows. Possibly also messaging apps.
I cannot fathom how someone wouldn't be able to appreciate working on a UWQHD monitor.
Actually, it's quite simple - here is a 27" 1920x1920 square monitor you can buy on amazon:
https://www.amazon.com/FlexScan-EV2730QFX-Monitor-1920x1920-...
I have one and I think it's great. I actually prefer splitting a 16x10 monitor into two halves, but the perfectly square monitor is great for diagnostics/monitoring where I can split it into four equally sized quadrants and see four things at once...
I'd still probably choose 16:10 because it's close enough, but 16:9 bugs me to no end (LENOVO) when there's a huge bezel above and below the screen.
At high enough resolution the side bar development doesn't impede me anymore (1600x1200 seemed good, 1400x1050 a little less on my old Thinkpads).
If the Surface were just more reliable I'd consider it. Until them I'm still using Thinkpads (in spite of their own shortcomings).
The shit some people complain about , unbelieavable......
Also The Verge seems to think everyone uses maximised windows all the time, which is very 'The Verge' of them.
Not odd at all. '1080p' is probably the most common resolution on laptops sold today. They really fleeced us with the 'HD' marketing; laptop displays today are often lower res than they were ten years ago!
And it's 320 less lines horizontally.
What matters to you may not matter to the next person, because their use case is different from yours.
No matter what laptop (and monitor) manufacturers do with respect to aspect ratio, they're never going to please everyone with their design decision.
This is hacker news. Surely here we can complain that they're not made for programming. I also do a lot of writing and extra width is utterly useless for that.
Isn't the answer kinda simple? If Apple were to decide to offer non-widescreen laptops and they sold like hotcakes, everyone would follow suit. For better or worse, Apple sets the trends on laptop form factors.
Then all PC laptop manufacturers seemingly conspired to deny us the option to purchase anything, at any price point, with >1080 vertical pixels. (Thankfully Apple didn't follow this trend at the time.)
Of course now with all the 4k/5k/high-DPI stuff we might finally be moving past that, but I haven't gone PC laptop shopping in a long time.