Re:Introducing the new Google+
by moonchrome on Tuesday November 17, 2015 @09:25PM
(#10585520)
>I think the issue is - who gets to decide how wide the content is. Is it the user or the website? Or to put it another way, does the act of maximizing a window represent an intent or does it represent a default error state that needs to be worked around by laying out the content in a different way.
This is why CSS exists - it separates style from content - if you want what that site has just disable all CSS and you'll get raw content.
>What are those non-subjective reasons?
There are things like optimal line length based on eye travel distance and a bunch of "defaults" that have been found trough centuries of experience in design/print. I don't do design professionally so I don't remember the exact rules but I did take design classes back in high school so I know they exist - I'll let someone who's an expert fill in on what they are :D
What gets me with MFWS, it's that when I really read something, when in flow and only the ideas behind the words matters to me, no amount of presentation will ever help or be of any importance. The most valuable ideas I got were written in old busted books with bare typesetting.
I think the issue is - who gets to decide how wide the content is. Is it the user or the website? Or to put it another way, does the act of maximizing a window represent an intent or does it represent a default error state that needs to be worked around by laying out the content in a different way.
I think that the user should get to decide how wide they want the content to be. For almost all GUI applications 'Maximize' has always meant "I want to see more of it".
>There are good reasons for things in design like column/page width/ratios, margins, line spacing, font family/size etc. purely from usability standpoint (ignoring subjective/stylistic choices).
What are those non-subjective reasons?