Editing Talk:277: Long Light
Please sign your posts with ~~~~ |
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 1: | Line 1: | ||
+ | Does the engineer come from a party? He is holding in his hand one of those red cups that already appeared in other comics. Thus he may be slightly drunk at that moment. [[Special:Contributions/141.101.104.165|141.101.104.165]] 09:03, 11 January 2016 (UTC) | ||
+ | |||
The driver seems to know that the light always takes forever and yet there he is. Sometimes people get what they deserve. {{unsigned|99.234.144.69}} | The driver seems to know that the light always takes forever and yet there he is. Sometimes people get what they deserve. {{unsigned|99.234.144.69}} | ||
Line 8: | Line 10: | ||
:I am a traffic engineer, and there are lots of reasons why intersections are designed as they are, and lots of reasons why they don't live up to expectations. Aside from the inherent difficulty of predicting traffic, there are issues centring around when the intersection was designed and when the user experiences it (this can be decades), the availability of data on the subject (in all but the densest/busiest areas most people would be surprised how little data there is, I think), and just the sheer expense of some "simple" solutions. For example, ...16.171's jurisdiction may not consider worth ~$100 000 to put in a sensor just so the occasional driver who wants to turn left from a low-volume approach only waits 20 seconds instead of 60.[[Special:Contributions/108.162.219.102|108.162.219.102]] 22:27, 26 May 2015 (UTC) | :I am a traffic engineer, and there are lots of reasons why intersections are designed as they are, and lots of reasons why they don't live up to expectations. Aside from the inherent difficulty of predicting traffic, there are issues centring around when the intersection was designed and when the user experiences it (this can be decades), the availability of data on the subject (in all but the densest/busiest areas most people would be surprised how little data there is, I think), and just the sheer expense of some "simple" solutions. For example, ...16.171's jurisdiction may not consider worth ~$100 000 to put in a sensor just so the occasional driver who wants to turn left from a low-volume approach only waits 20 seconds instead of 60.[[Special:Contributions/108.162.219.102|108.162.219.102]] 22:27, 26 May 2015 (UTC) | ||
− | [[Special:Contributions/108.162.250.203|108.162.250.203]] 06:44, 27 April 2014 (UTC)Doesn't mean Cueball can't reverse away to get the engineer off his . Unless it's a one-way street. | + | [[Special:Contributions/108.162.250.203|108.162.250.203]] 06:44, 27 April 2014 (UTC)Doesn't mean Cueball can't reverse away to get the engineer off his car. Unless it's a one-way street. |
− | :Or there's another | + | :Or there's another car behind him that we can't see because of reasons of artistic brevity. -Pennpenn [[Special:Contributions/108.162.249.221|108.162.249.221]] 04:50, 6 February 2015 (UTC) |
− | |||
− | |||
− | |||
The punchline gets funnier based on how far away you are from the forthcoming Tuesday. Only share this comic on Wednesdays. {{unsigned ip|108.162.216.71}} | The punchline gets funnier based on how far away you are from the forthcoming Tuesday. Only share this comic on Wednesdays. {{unsigned ip|108.162.216.71}} | ||
− | |||
− | |||
− | |||
− |