Obviously depends on your city, but in here in Vancouver all buses have bike racks on them. So biking one way is a matter of tossing the bike onto the bus on the way in and riding home or vice versa. I tend to do that, but I have a 40 mile commute and cycling both ways in one day is a bit excessive for me.

One of the google talks by Violet Blue actually had some interesting information on the 2257 requirement. She did not go quite this far in criticising the law, but pointed out some very serious problems with it.

Basically, a decent chunk of people who needed to prove age for 2257 compliance basically just had pictures of them with the driver's license. Of course, many people tend not to perform under their real name and if these pictures get onto the internet, then someone else can tie a face to a real name and possibly even an address. Not a good situation in general. From what I gather, the wording of the law was pretty vague as well as to what sort of proof was required and who could eventually ask for it.

Anyhow, a pretty interesting talk here with some relevance to the topic: Violet Blue (Google Tech Talks)

It's not the first time that any huge defects have been caused by a single character. Quoting Code Complete who in turned was referencing an article from the early 80's (Kill that Code, Gerald Weinberg), "...three of the most expensive software errors of all time-costing $1.8 billion, $900 million and $245 million- involved the change of a single character in a previously correct program. So on the one hand, it's easy to sort of snicker that they were so close to having a correct implementation, but just missed, but on the other hand, there is a long and storied history of us programmers blowing things by a single character. I mean, isn't the 'off by one' error still one of the most common ones in development code, a instead of =, index instead of index-1 or whatever? At least now that the defect has been isolated and can be fixed. One character fix is much better than a full redesign...