"Usage: http://httpcats.herokuapp.com/[http_status_code]"

And hey, Adam wrote chapter 13! Nice!

Terrible, *terrible* name.

A good explanation for some of the basic weirdnesses of Javascript (I find Crockford to be a bit opaque on some of these points, so it's nice to get a second opinion).

"First of all, NodeJS is crazy fast. Dahl showed one benchmark that had it beating out Nginx. (However, as he admitted, it was an unfair comparison since he was comparing NodeJS serving something out of memory with Nginx serving something from disk.)" -- Weirdest sentence I've read all day. ("However, as he admitted, it was an unfair comparison since he was comparing NodeJS which was driving a Ferrari with Nginx which was participating in a three-legged race with its 80-year-old grandfather.")

Initialization blocks, which are executed before the constructor.  This is actually a completely timely piece of advice for me.

"In this paper, we use tools from Kolmogorov complexity and algorithmic information theory to show that sampling and search problems are essentially equivalent. More precisely, for any sampling problem S, there exists a search problem R_S such that, if C is any "reasonable" complexity class, then R_S is in the search version of C if and only if S is in the sampling version."

Are the widths (lengths, whatevs) of the horizontal lines proportional to time? What other kinds of tasks could these diagrams be used for? Could we automatically generate these kinds of visualizations from (say) a protocol description? (I'm thinking of something like Biocoder here.)

"It is still controversial whether global warming from CO2 is occurring or whether recent warm years are a statistical fluctuation or a consequence of changes in the sun." -- I didn't realize that John McCarthy (of LISP fame) was a climate-change skeptic. Fascinating. Sort of.

"(The terrible thing is that we regard the call instruction as a primitive and a tail-call as a hack, when it is much more fruitful to regard the tail-call (a goto) as primitive and the call instruction as an optimization. Why? Because the latter theory consumes less stack space.)" -- enlightenment, via Guy Steele. See also this comment : "The continuation that obeys only obvious stack semantics // O grasshopper, is not the true continuation. :-)"
( http://people.csail.mit.edu/gregs/ll1-discuss-archive-html/msg01389.html )

"But not me."

One user's notes...

Free software for the same! Even better.

Someone else *has* had this idea! $8, and on the Mac. I gotta finish my own, personal implementation of this...

Google talk video.

Yet another example of why (I still maintain) that the GINA law has a big ole' loophole in it.

"My Stats homework has a question of the type: "Given this joint distribution over X and Y, compute E(E(X|Y))."... This notation is extremely confusing.Given how unclear the notation is, I decided to do something about it, using the formal(ish?) language that I designed yesterday..." --- A(nother) interesting attempt at a "formal language with types" approach to probabilistic notation. It's good! But to be honest, I think ideas like this occur to a lot of Haskell-aware CS people when they first encounter probabalistic notation -- I remember John Barnett showing me something like this four or five years ago. I'd recommend looking at some of the papers of Avi Pfeffer and Claire Jones, if you want to see where this stuff ends up going. In particular, Pfeffer's 2000 thesis, or his IBAL paper, or his "Stochastic Lambda Calculus and Monads of Probability Distributions" paper, and the references therein. Things get interesting when you go to higher-order modeling languages...

"Indiemapper is the smarter, easier, more elegant way to make thematic maps from digital data."

I feel duty-bound to forward this on to you...

Class notes from a course taught by Stephen Fienberg. Includes an index of readings, as well as a link to a preliminary book (paper anthology, edited by, among others, Fienberg, Blei, and Xing) on the same.

Wow, this book sure would be an awesome gift.

PDFs of the out-of-print book, "Artificial Intelligence and Molecular Biology." When I first saw this, I thought, "meh." But then I looked a little closer -- chapter 2 by David Searls, chapter 8 from Peter Karp, and few others that look quite interesting as well. The whole thing is a little old, but good ideas never go out of style. Definitely worth a closer look.

"Explaining why a study of bear DNA isn't ridiculous takes long enough that the average uninformed voter will tune out long before the key point is reached." Really? Has someone actually tried this? At any rate, the general point that "science is too important not to be funded by the government at a large scale" might be right -- but asserting it just begs the question. Try telling this to (a) Robin Hanson, or (b) anyone from the Broad Insititute.

A library for browser-independent graphics programming in Javascript.

Honestly, all these people who are complaining about the del.icio.us redesign are completely missing the point. Sure, the layout is weird. Sure the colors need improvement. Sure, there are a whole host of other tweaks that could be made. But! Three things: (a) 1000 character comments, (b) working (and good!) search, and (c) better handling of tag bundles. "Good" web design pales in the face of real, useful features. If you spent your life studying web design instead of web programming -- well, sorry you wasted your life, guy.

Notice the bug with ID #1.

MCMC in Python. BUGS-like. Good examples.

"Free toolkit for developing mapping applications..."