5 ms·

Here is a motherfuckingwebsite as an example: http://motherfuckingwebsite.com/ http://motherfuckingwebsite.com/

vinceguidry 13y ago
Please don't do a serious website without a container div limiting the width of the reading area. Most people with laptops keep their browser windows maximized, and resizing the window just to read one article is a huge pain in the ass. I usually just decide not to bother. Otherwise that website's great.
- teddyh 13y ago
  Well, maybe they shouldn’t do that, then. If they don’t want a web site that wide, they shouldn’t make the web browser window that wide. (Oh, I forgot that the web browser is not an application, but a platform and an OS in its own right, and has replaced the native OS. Silly me.)
  - vinceguidry 13y ago
    One day you nerds will realize that technology serves people, not the other way around. I can't wait for that day.
    - maxerickson 13y ago
      Are you talking about the web browser or the web page here? Or maybe the OS/DE that makes it awkward to split the screen/size the window to reading width? Or the laptop, with it's silly form factor? But sure, everyone that publishes some text better make sure they account for every context that it might get viewed in. In the spirit of offering solutions, here's some code you can use to add a 'Narrow' button to your browser: https://gist.github.com/maxerickson/7771860 https://gist.github.com/maxerickson/7771860
      - vinceguidry 13y ago
        I'm talking about a simple container div. Works everywhere.
        maxerickson 13y ago
        Yes, I understood you. I thought it was bizarre that you thought having every author of a webpage put some noise in their code was the right place to fix your technology stack.
        vinceguidry 13y ago
        It's not noise, it's presentation markup. That's what HTML/CSS is for. To manage the presentation of information. It's not that hard. Learn a little responsive CSS and have the div go away if the browser's width drops below, say, 600px. Visual presentation is a hard problem, has been ever since the tele-type days. You're always going to need some "noise". I'm not saying you have to go full-hog with design bling, but you should at least learn enough about responsive CSS so that your site is usable across the three main types of screen it will be displayed on.
        maxerickson 13y ago
        I would still argue that making the browser aware of the screen it is using (or perhaps, aware of the screen real estate it currently occupies and the text size preference of the user) is a better solution than adding a div to every serious web page. Also, I'm pretty sure that (at least for simple pages) styling the body element will work just as well.
        vinceguidry 13y ago
        Why would that be any better? The only thing the page displaying in any browser needs to be aware of is how big the viewing window is, and the DPI. With those two pieces of information, you can have anything that runs in a browser present a useful interface. That way content can handle all the edge cases that different screens can throw at them. And different browsers can handle things like text sizes the way they want to. You don't want to have to make individual websites cater to individual screens or browsers. There's just too many of both. The interface between them needs to be a loose coupling.
- dllthomas 13y ago
  Is there some third way? Occasionally I really want it that wide, and if there's a div there's no way (short of firebug or grease monkey) to get it. At the same time, as someone who quite frequently has windows maximized, I feel some of your pain - though "ctrl-f S <read> ctrl-f Q" isn't exactly a "huge pain in the ass".

Please don't do a serious website without a container div limiting the width of the reading area. Most people with laptops keep their browser windows maximized, and resizing the window just to read one article is a huge pain in the ass. I usually just decide not to bother. Otherwise that website's great.

teddyh 13y ago
Well, maybe they shouldn’t do that, then. If they don’t want a web site that wide, they shouldn’t make the web browser window that wide. (Oh, I forgot that the web browser is not an application, but a platform and an OS in its own right, and has replaced the native OS. Silly me.)
- vinceguidry 13y ago
  One day you nerds will realize that technology serves people, not the other way around. I can't wait for that day.
  - maxerickson 13y ago
    Are you talking about the web browser or the web page here? Or maybe the OS/DE that makes it awkward to split the screen/size the window to reading width? Or the laptop, with it's silly form factor? But sure, everyone that publishes some text better make sure they account for every context that it might get viewed in. In the spirit of offering solutions, here's some code you can use to add a 'Narrow' button to your browser: https://gist.github.com/maxerickson/7771860 https://gist.github.com/maxerickson/7771860
    - vinceguidry 13y ago
      I'm talking about a simple container div. Works everywhere.
      - maxerickson 13y ago
        Yes, I understood you. I thought it was bizarre that you thought having every author of a webpage put some noise in their code was the right place to fix your technology stack.
        vinceguidry 13y ago
        It's not noise, it's presentation markup. That's what HTML/CSS is for. To manage the presentation of information. It's not that hard. Learn a little responsive CSS and have the div go away if the browser's width drops below, say, 600px. Visual presentation is a hard problem, has been ever since the tele-type days. You're always going to need some "noise". I'm not saying you have to go full-hog with design bling, but you should at least learn enough about responsive CSS so that your site is usable across the three main types of screen it will be displayed on.
        maxerickson 13y ago
        I would still argue that making the browser aware of the screen it is using (or perhaps, aware of the screen real estate it currently occupies and the text size preference of the user) is a better solution than adding a div to every serious web page. Also, I'm pretty sure that (at least for simple pages) styling the body element will work just as well.
        vinceguidry 13y ago
        Why would that be any better? The only thing the page displaying in any browser needs to be aware of is how big the viewing window is, and the DPI. With those two pieces of information, you can have anything that runs in a browser present a useful interface. That way content can handle all the edge cases that different screens can throw at them. And different browsers can handle things like text sizes the way they want to. You don't want to have to make individual websites cater to individual screens or browsers. There's just too many of both. The interface between them needs to be a loose coupling.
dllthomas 13y ago
Is there some third way? Occasionally I really want it that wide, and if there's a div there's no way (short of firebug or grease monkey) to get it. At the same time, as someone who quite frequently has windows maximized, I feel some of your pain - though "ctrl-f S <read> ctrl-f Q" isn't exactly a "huge pain in the ass".