I clicked on this link due to the simply awesome title, but realized the author had a great point. When asking "how does this look" what we really mean is "is

I clicked on this link due to the simply awesome title, but realized the author had a great point. When asking "how does this look" what we really mean is "is this rendering the way I want". He posits that to properly answer this question, you must ask "on what", but my feeling is that you need to split the question into textual formatting (which can stay the same on all devices) and layout (which might be adjusted for the device). In the old days (yes ... I'm old), we used WordStar on CP/M and we were careful to use our limited formatting features to maximize the impact of our words. We had bold, underline and (sometimes) even italics. When we composed our text, we assumed we'd use 55 of the 66 lines on the paper, and 75-80 characters across the page (depending on margins). We did this because that's what a 12 CPI typewriter would do. If we moved to a different printer, it might not be able to produce the exact same document, but with a few exceptions, we could live with the changes to the line wrapping and simply print it. The problem introduced to printing when laser printers arrived (yes ... you could do cheesy images on dot-matrix printers) was that we now had to flow around images, account for multiple text sizes and pitches. As the web matured, we never quite completely separated the text formatting from the layout. My recommendation is that you focus on the formatting of your text when writing. Let the designer figure out how the layout needs to change when "responsive design calls".