Yeah, a lot of websites these days seem to block or mess up autofill where I actually want it: I can’t say how many websites break credit card autocomplete, TOTP code autocomplete (e.g. via Apple’s native TOTP implementation), username/password autocomplete. I can never really tell if it’s incompetence or a misguided idea of security, but it’s extremely annoying.
It can get even smaller when loose objects get packed into packfiles because of delta compression: a whole bunch of identical files can be stored in minimal overhead over storing one copy.
Right, packfile size is really what matters in the long-term. A tiny change to a file in the short term just adds the whole thing again (compressed), whereas a tiny change in a packfile shouldn't add much at all. Unless you've got very limited disk space, the long-term is the only size that matters.
Google Buzz also seemed like a better path for Google to have a "social network" than what they tried to do with G+: Post short twitter-like things from various Google properties and have your friends posts show up in the same place. Between Buzz, Reader and gmail chat, Google had a fairly solid lineup of social products that they killed one way or another to boost G+.
I had a cohort of friends from grad school that used Buzz like crazy. We tried Google+, but it just wasn't as useful. This would have been 2008-2010.
We also really wanted to use Google Wave, but couldn't get enough invitations to go around. It was like nobody at Google figured out that the only reason invitations worked for Gmail was because Gmail was interoperable with email. Wave didn't interoperate with anything. Either your friends were on it and you could use it, or they weren't and you couldn't. 3-4 invitations after a couple months just wasn't enough of a social effect to make it useful like it had been for Gmail.
sbcl can compile to a single executable (the image is embedded in the binary). From a deployment standpoint, the only real issue is if you depend on a dynamically linked C library like OpenSSL.
I used to do this to build command line utilities in SBCL, with millisecond initialization times. Good technique, and compress the image so executables are fairly small.
Yeah, I’ve done that in a slightly hacky way (manually run the various stages of the sbcl build and statically link c libs before building the actual image).
The two arg cd is pretty useful (and, zsh implements it too because cd is a shell feature): if you have parallel directory structure (e.g. the way rails does tests) you can switch from app/b/c/d to spec/b/c/f by doing `cd app spec`
reply