Yikes. D sounds interesting, but this is pretty unappealing stuff.

James Hamilton: "The FriendFeed technique to deal with the schema change issue is arguably a bit heavy handed: they simply don’t show the schema to MySQL and, instead, use it as a key-value store where the values are either JSON objects or Python dictionaries."

The Guardian's Paul Carr takes on both parties of the TechCrunch vs Last.fm dispute. Both are deemed incompetent.

"The 'Web Operating System' just highlights how much journalists don't know about computers."

"The Web Client is unimplementable."

A great summary. App Engine is perfect for toys like my http://downforeveryoneorjustme.com, but even then it has problems with quotas. It's pretty much the opposite of "instant scalability" for now.

Something to come back to once I've spent a significant amount of time with a large Scala code base. Thus far, pattern matching in Scala seems fairly maintainable.

So, because Facebook fucked up with the beacon thing we're all gonna use email forever. Dag.

I'm fairly neutral about OpenID, and I think the spec itself is fairly explicit about not attempting to solve the problems listed herein. That said, there's a ton of real-world, right-now problems to tackle here.

Katz echos what I've heard elsewhere: Erlang is great for server-side stuff but has no place on the front-end or as the "one true language" for a bi project. The memory allocation stuff is a bit shocking, though.

This sort of thing seems more relevant to programmers who suffered the years of hype around OOP. To someone younger, it seems like OOP and other styles of programming all pretty much get along.

Really excellent run-down of why Android has some serious hurdles to jump.

the Data Mining blog rips apart Time's idiotic non-choice for Person of the Year

looks like people are catching on ;)