The site looks fine under the current Firefox, but is badly broken under Seamonkey 1.1 (Which I still use regularly. Sue me.) See the screenshot here:

http://i.imgur.com/VePRd.jpg

Absolutely true. I'm in IT at a Big Pharma, and I've seen plenty of those exact kinds of issues during regression testing - patches "breaking" little loopholes in Windows behavior that we'd unwisely come to depend on in some obscure cases. That XP SP2-to-SP3 upgrade buggers up DCOM, for example.

Came for the inevitable pr0n/"I'm thinking Arby's!" post, leaving somewhat satisfied and somewhat,... distracted.

Came here for the "did they also grow some miniature fava beans and miniature chiantis?" question,.... leaving happy.

Seconded.

2013487. Srsly.

I heard Toyota and Chevrolet had partnered on an attempt to achieve this same design. They were gonna call it the Toyolet.

To improve mileage, all you needed to do was put a brick in the tank.

The first prototypes were kinda cheap, though - the seats had two positions: up and down.

From the radio show "X Minus One":

http://otr.relicradio.com/2010/03/sf94-the-category-inventor-by-x-minus-one/

Agreeing with the Model M comment.

Also: obligatory one-handed typing joke, taken as read.

Also, less facetiously, I wonder how well it accommodates switching scripts/Unicode ranges or special typing for codepoints. (Haven't yet rtfa.)

I was thinking about that myself; I imagine ID10-T as the whole class of errors, and the PICNIC, PEBKAC and all others as specific examples (though so many of them are redundant).

OK, so we know now that just pointing out the facts doesn't work. What does? Have any studies identified techniques that actually work?

Proposing a new lUser acronym:

PIDSNIT - Problem In Driver's Seat, Not In Throttle.

Picasa stores some things, including titles and tags, in IPTC data within the image files themselves. This is great, since it lets you carry these things around with the files when you move them to another image viewer, etc.

I wish it did the same thing with albums, but album data is stored in a separate file. In principle there are IPTC tags (like "collections") that could be used to record album-membership information within the image file itself, but Picasa doesn't do it that way.

The event horizon isn't wavelength-dependent. It's the place where the escape velocity equals the speed of light.

Black holes that evaporate due to Hawking radiation don't leave behind a naked singularity. They're just gone.

My company would find it worth the money (if I and a few others could convince them to, and if the affected users could actually be corralled to install and use it consistently, and nevermind the internal stresses between the graphic designers vs. marketing vs. regulatory agencies vs. the ridiculous turnover in parties responsible for copy) to buy a couple fonts that include every damn Unicode codepage that we'd reasonably need to use. Right now, the only one I've found easily available (and I'm not a deep expert in this, but am learning) is Microsoft's Arial Unicode MS, which is sans serif, and we'd kinda like a serif'd one, too. There are a few other nice ones that include a fair selection of codepages, but it seems that they still manage to leave out one or more that we actually find critical, so we can't pull all locations in line.

(The application here is packaging materials for pharma, and I support this department and these processes in an organization with printing needs in at least 30-some countries.)

(Also, could care less about eliminating Comic Sans, but Microsoft's Symbol font can go jump off a bridge; it's buried so deeply, treated so weirdly, and is so thoroughly Unicode non-compliant that it manages to sneak in and bugger up documents at almost every stage in our development processes. I'd like to slap the person responsible.)