With high-resolution monitors becoming more popular, does the StackExchange team have any plans to make these websites use more display area when the browser is maximized/fullscreen?
Currently, I am using a full HD display (1920x1080). Only about 3/7 of the width of my display is used on StackExchange sites:
---------------------------------------------------------------------------------
| || || |
| || || |
| || || |
| || || |
| || || |
| <---- UNUSED ----> || <------------ 960px ----------> || <---- UNUSED ----> |
| || || |
| || || |
| || || |
| || || |
| || || |
...
---------------------------------------------------------------------------------
In addition, with current 2560w displays and future high-resolution displays, the amount of unused space is greater than the space used to display content.
In my opinion, the horizontal layout should be fluid - proportionally adjusting to the width of your browser window to maximize the use of your display. It probably shouldn't expand to fit the entire width of the window, because that would require users constantly turn their heads to view all of the content.
This similar question has valid arguments:
(1) I like being able to size my browser window to hide the panel on the right without losing question/answer size now and then (mainly when I'm working on two things at once).
(2) I like knowing approximately how my answers will look in terms of paragraph size and so forth.
(3) I like knowing that syntax highlighter wrapped things correctly.
(4) Mostly, I like that this helps encourage brevity in code samples - if the sample is long enough that you're losing code for nesting reasons, it's time to re-focus your thoughts and pare down to just what's relevant to the problem.
My counter-arguments:
(1) Add a "collapse side panel" feature that remembers your preference.
(2) Why does this matter? A high-quality answer will contain only relevant and necessary information. (Maybe restrict post length for new users?) Also, see point (3) below.
(3) Never depend on the code formatter correctly wraping/indenting code. You can preview posts below the editor anyway.
(4) This will happen in posts regardless of the width of the page. Even with this 960px-wide page, some users constantly dump entire programs into a post. See parenthetical in point (2).
Does the community have any thoughts or suggestions on this matter?