iPad for me. No fancy Flash fonts but reading nicely.

iMac so far, maybe iPad in 2012

Primarily on my laptop but increasingly using an iPhone, including this response.

ThinkPad
iPad

iMac, Android. Home page takes a while to load on Android.

Not what OS, what device.

Plus I'm hoping more for a method, not just data.
If somebody asks "How do you make ice-cream?" don't say "Rainbow Sherbet!!" :-)

hhp

Lenovo x301 laptop computer
HTC HD7 smartphone

Hrant, you clearly don’t read Typophile on many different devices, otherwise you would notice that inserting line breaks by hand to make your paragraphs nicer do not always reflow well on different settings, making your efforts not only pointless, but counterproductive. Not picking-on here, just saying.

MacBook (most frequent)
PC with Viewsonic LCD monitor (less frequent)
Backberry (hardly ever).

Grzegorz, that's actually what I'm trying to resolve:
http://typophile.com/node/88503#comment-488380

However I do think your conclusion is simplistic. To
me the point of a block of text isn't to look nice, it's to
be read. So I have to wonder what's worse: a paragraph
that's hard to read on most devices (because the lines
are way too long) or one that looks funny on some? Sure
funny lines aren't great, but missing the line return
every single time (or in practice, having to do the line
return very slowly in order to avoid missing the landing)
is worse. Most long posts (i.e. posts that contain long
paragraphs) on Typophile are quite daunting to read
because they look like that slab from Space Odyssey.

Hence the question I pose here. So if enough people view
Typophile on small screens what I should ideally do is go
even narrower on my measure. More work for me (because
it gets harder to have a non-distracting rag), but hey, that's
what Design is about.

hhp

iMac (mostly), but also iPad and MacBook when I’m away from the studio.

iMac unless I am traveling.

The Punchcut guys may have automated statistics on site usage. You might check with Jared.

Good idea - email (with a nice rag :-) sent.

hhp

The environment variables give just part of the story. For instance, now the log should read something like HTTP_USER_AGENT=Mozilla/5.0 (Macintosh; Intel Mac OS X 10_6_8) AppleWebKit/534.52.7 (KHTML, like Gecko) Version/5.1.2 Safari/534.52.7 SERVER_PORT=80 for me. That is just part of the story because I am now on a Mini with a Flatron LG screen. Other times I am on a MacBook Pro and I can also be on a mini with a 25' Mac screen. The log does not tell that. I can also be on an iPad, during the week end.

Two tin cans connected to my cable modem with cat5 cable. When the hamsters have enough food to spin the wheel we occasionally get the wifi to work, but only until the cat comes in and scares the hamsters.

Indeed, I should have read this post. Maybe the logs then give enough information.

Media query.

MacBook Pro mostly (but cinema monitor). iPhone 4 about 25% of the time.

But I’m also using an alternate [beta] theme that Jared asked me to try out. (Not better, really, just different — and definitely worse on iDevices; hmm, I should probably switch back now.)

MacPro with two 23-inch screens, one of which provides a viewport for Safari (two thirds of screen). iPad2 usage rising (even with fall back headings very nice) — around 30% I guess.
I try to avoid doing Typophile on my iPhone 4S because that is not a pleasant experience at all.

iMac 27″ (Camino) / Windows box with 1440x900px monitor (Firefox, maximized).

So I have to wonder what's worse: a paragraph that's hard to read on most devices (because the lines are way too long) or one that looks funny on some?

I always take for granted that the display does the wrap around. What device does'nt?

But they wrap as late as possible, ignoring
the needs of the human reading "hardware".

hhp

The thing is, Hrant writes poetry, not prose! ;-)

What I try
is poetry
for the eye! ;-)

hhp

An Armenian, assertive in tone,
whose love of notan stands alone,
adds increasingly short breaks:
"Whatever it takes
to make my rants work on your phone!"

Suggestion for rephrasing the bum:

'... adds ever shorter breaks:
"Whatever it takes
to make my (H)rants work on a phone!"'

Aside: I do not have a smartphone, so I read none of Typophile on such a device. It's all on a desktop 'puter.

Actually the irony is that if most people used phones to
read Typophile I wouldn't need to worry about manual
linebreaking since the line measure is plenty short! :-)

hhp

I wouldn't worry about it anyway, the percentage of people who would be happy with your line breaks are equally matched by those who would not be so it is a wash.

1) Actually if the responses in this thread are any
indication few people read Typophile on small screens
so they don't see the funny linebreaks Craig showed.
2) Making the measure even shorter would avoid those.
3) Ease of reading is not a conscious preference.

The way I see it, choosing to believe that manual linebreaks
either don't matter or are actually harmful is a convenient
assumption meant to save effort. But hey, if I wanted to save
myself effort that most people don't appreciate I wouldn't be
designing type! :-)

hhp

But, Hrant, if you spend less time doing line breaks, you would have more time to design type ;-)

Google analytics tells you that in a second, provided they have it set up. My guess would be <1% use smartphones.

iMac