I'm pretty sure the speakers were still there when we left.

It's the wrong typeface.

We care. We're working on it.

Appreciate the responsiveness. But forcing us to use your link shortener does not send a message of "we care"

What I meant was that we care about uptime, and we're working on improving that.

When we accept complexity while striving for simplicity, we end up with actual features.

And a diminished ability to add features in the future.

Why doesn't this use the userData for IE 6/7? Given that those browsers are the least performant, wouldn't it make sense to ensure caching works on them?

As I pointed out below, Amplify.js, an established Javascript library, has the Store module that supports all manner of browser storage (including userData) with a unified interface that abstracts away the specific storage mechanism.

http://amplifyjs.com/api/store/

I have nothing to do with that project but I hate to see people re-invent the wheel. ;-)

Simply because I didn't know about it. Happy look at pull requests or I'll have a go at it myself if I get time.

You prepend 'js-' to a selector, not append it. Otherwise you'd end up with 'my-thingjs-', which is weird.

Also, no semicolons, yey. Coffeescript, boo.

Why isn't TextMate on the list?

added

Shortcut key: g and then m.

as a vim user, the space in my brain that holds keyboard shortcuts is entirely full.

I never use any keyboard shortcuts on web apps.

Twitter has a business model. It's working fine. See: http://www.businessinsider.com/exclusive-interview-twitter-c...