Yeah, it was kind of a "hey it does it for free" sort of thing.
I mean, if it's never really a problem, why spend more time setting extra things up. That being said, I'd have no problem setting up and managing HAProxy if we wanted to do that.
The fw boxes are from these guys: http://www.watchguard.com/ They were X550e's this weekend we're installing XTM 515's
Tooting my own horn here, but I'm working on a book covering the Go Standard Library. Still in progress, and not at the sync package yet, but it's coming along. Check it out if you feel inclined.
It can work the same way. You just slowly figure out the hash: this pw for this user was a bit faster than all the other failures, so we know the first byte of the hash is ...
If you have a bunch of hashes precomputed, you can start to figure things out pretty quick.
The point is it's still leaking information about what's going on.
I do have the sentence "This difference is enough to measure, even on web applications." in the fourth paragraph. Should I highlight that a bit, bold maybe?
I'd also like a good reference for that, and my Google skills were failing me. Do you happen to have a link to something show that off?
1. The Xcode 4 download compared to Xcode 3 is basically just a different IDE. The gcc version is, for all intents and purposes, identical. There's nothing stopping anybody from just installing that if all they need is the toolchain.
2. The other big 2 OS's (Windows and Ubuntu) don't have any build tools installed by default either. Granted they are just an apt-get away on Ubuntu, but it's still something you have to explicitly install.
3. If I wasn't a dev, I'd be pissed to find some compiler toolchain IDE gongshow eating up 5-15GB of my disk space, so not having it by default is probably a good thing. Most people aren't devs.
I paid the $5, but I'd still like to see just the toolchain available as a free download, though I still don't think it would be a good thing to have it installed by default.
Ahh I see according to http://lnkr.mobi/bm/google_bookmarks_api/ that is about all the docs on that API there are, and it doesn't support annotations/notes. Mine doesn't either, but it's a one line change to make it do so.