This is worth proposing. A tag where fallback text is provided within which can be overridden by the browser with a formatted date string would be excellent.
I have a 30-minute walking commute to work, and changing back to non-automated buttons has added about 5 minutes to that if I'm not super lucky with timing. The worst is seeing the lights turn and knowing it would have lit up green for pedestrians only to have to wait a full cycle for the next opportunity.
We're hiring across a range of engineering positions. But the coolest is definitely this one:
"Contribute to a next generation JavaScript library for indoor mapping, which utilizes WebGL, physics, indoor positioning, and wayfinding. The engineer will be responsible for adding new features and apply performance improvements to the existing code base. You will solve challenging problems like applying performant collision detection algorithms for UI elements, or creating a solution for turn-by-turn directions. We are changing the game for indoor mapping, positioning, and wayfinding, as well as some top-secret research ideas (Pst - there will be robots).
I've just finished reading The Lean Startup. There is so much in there that is relevant to this if you haven't already read it I highly recommend you check it out. Especially the sections on engines of growth and metrics.
Two things me sane: I get up an hour earlier than I need to in the morning to sit, think (high level/long term), plan and occasionally write. I set "Do not disturb" on my phone to automatically enable at 6pm daily.
My approach is to leave it to the device manufacturer/user and only use % based font sizing. CSS wise, for layout I then rely on % for horizontal spacing/positioning and em's for the verticals, which act as a kind of "em = line" system. Even though an em is rarely a line is a baseline sense, it makes cross-device design a lot more painless leaving the base unit to the device itself.
What you need to do is use a 'touchUpInside' event, there are a couple wwdc preso's that cover it. Basically you compare coords of a touchend event to the coords of the target. Touchend events fire instantly so you dont have to worry about the 300ms click delay. Dug this out of some old code, wont work out of the box but you get the gist. https://gist.github.com/3067704