As shown at right, Netflix is suggesting I should get The Last King Of Scotland because I liked Little Miss Sunshine. One suspects their algorithm contest has not borne the sweetest fruit.
You know, IE7 looks like a reasonable browser, but it’s not. To prove this it’s not even necessary to resort to something like CSS compliance, where no one else gets it entirely right either. It doesn’t even get HTTP right. That is, when confronted with a perfectly legitimate 204 status code if fucks up. Spectacularly.
Now why would someone be using a 204 status code? Well let’s look at the language in the standard:
10.2.5 204 No Content
The server has fulfilled the request but does not need to return an entity-body, and might want to return updated metainformation. The response MAY include new or updated metainformation in the form of entity-headers, which if present SHOULD be associated with the requested variant.
If the client is a user agent, it SHOULD NOT change its document view from that which caused the request to be sent. This response is primarily intended to allow input for actions to take place without causing a change to the user agent’s active document view, although any new or updated metainformation SHOULD be applied to the document currently in the user agent’s active view.
The 204 response MUST NOT include a message-body, and thus is always terminated by the first empty line after the header fields.
Needless to say, if you’re doing ajax-style processing, and, say, letting people delete stuff out of a list, then having a code that let’s you say, “Yeah, we succeeded, there’s nothing more for us to say, nor any need for you to redisplay or anything, though.” is pretty damned useful.
Would you like to know what IE does to the 204 response code? It changes it to 1223.
For those not inculcated in the minutia of HTTP, all response codes are three digits, with the first digit indicating the general category of response (1 is informational, 2 is success, 3 is redirection, 4 is for client errors, 5 is for server errors), and the additional digits giving more specific information. 1223 isn’t even on the map here.
This has been a problem for at least five months, since that’s when a bug was filed in the dojo toolkit’s trac about it.
How can Microsoft be taken seriously? All that money, all those programmers, and they can’t do better than this?
I wish I had had Rhyme & Reason back when I was actually writing poetry. From the FAQ:
Rhyme & Reason is a suite of online tools for poets and lyricists. It includes an editor for writing verse, an integrated dictionary, rhyming dictionary and thesaurus for finding words, metrical scanning tools for identifying meter and rhyme scheme, as well as features that allow you to share your work with others and comment on other writers’ poems or lyrics.
Now I don’t really give a damn about rhyming dictionaries and thesauruses–I already know too many words, who needs more–but I was always having to look up the metrical stuff (what’s the stress pattern in a spondee again?), and having this done automatically would have been excellent.
At a few minutes past 11am today, we put Tucker to rest. He had just turned 19 on May 1st. He was unimaginably old, but up until the last week or so, he seemed comfortable and happy. He was still climbing on top of the television to get in his basket, and climbing up the stairs to visit me in my office when he got lonely.
Tucker had been with Anne since before I was, and he was always undoubtedly her cat. Over a period of years, though, he came to regard me as an adequate substitute if she wasn’t around.
Especially as his health had gradually declined the last couple of years, I spent more and more time taking care of him during the day–feeding him when he was hungry, trying to make up for the attention he no longer got from Ford, etc.
To say it’s wrenching to not have him around doesn’t do it justice. I know that, in time, the acuteness of the loss will fade. But right now it’s fresh and raw.