fortybillion

Orbital and Banco de Gaia on repeat soundtracked my CS degree. Both artists’ work from that era still hold up.

Settings -> Sounds & Haptics -> Change With Buttons: OFF. Now the volume controls will only ever change the audio volume and never the ringer volume.

This is legal in California.

Has anyone ever debunked or repeated the food-coloured white wine test? I've heard this one before and it always seemed very strange to me as white and red wines have such clearly distinguishable characteristics.

I actually find the omnibar incredibly frustrating, as I know when I want to search and I know when I want to find something from my history. For me, these are separate tasks and combining them makes me slower because I have to mentally filter out the unrelated results.

I'd love to see Google vs. Apple's research for one vs. the other. It seems to be one of the polarizing issues.

My behaviour is pretty much the same — Safari for personal browsing, Chrome for dev. Chrome is very nice, but Safari is a lot more "solid", especially when it comes to 3D Transforms and other advanced features.

Safari 5.1 on Lion isn't a life changer, but the gestures just feel right. Going back to Chrome feels like taking a step backwards, especially on a Magic Mouse where the double-finger-sideways swipe is still somewhat awkward.

Having used this extensively for development and testing over the past several hours, this is definitely "beta", but it's nice to see Google making the effort here.

Unfortunately for Chrome, Safari 5.1 has set a new standard for gesture support that will be hard to replicate (if they even care to, I'm not convinced Google actually cares about feeling 100% "native" on any OS).

Nested tables worked, but they were incredibly hard to write/edit by hand. This gives us a way of using those layout concepts while still maintaining some separation of document structure and layout definition.

The issue with columns in web browsers is the variance in screen height. Clearly it would be worse to render an entire long-form article in 3 columns, forcing the user to scroll back up to the top of the page to start reading the next column.

This forces the designer to break the content up into multiple column blocks based on a target screen height... so now we have the same problem, only on a different axis.