Doesn't quite mesh with the statistics I've heard. I've always heard that in a recession, the person with the lower education (assuming they're still qualified) is likely to get hired, because they're the one who is less likely to jump ship as soon as a better job comes around. It's the basic problem of being overqualified during a recession that a lot of people are facing.
I'll take my fixie internet any day. You probably don't have the taste to appreciate such things, though.
Grant hunting is a year-round sport, baby.
"On the eighth day god created turok" without vowels. Not that hard to remember.
There's not nearly as much solar wind that far out, I would think.
Hit shift+c to compose in a new window. Then you don't have to wait that OMG ETERNITY of 1-2 seconds to return to your inbox.
There once was a man from Japan
Whose limericks just wouldn't scan.
When asked why this was,
he said "It's because,
I always try to fit as many syllables onto the last line as I possibly can."
Also DHCP. Which is rather important in most networks, I'd think, no?
Basically, the simple answer is that in the Google Maps app, you have to tell the app when you've reached a turn. It doesn't detect it. (So you have to hit "Next" a bunch of times through your route) The TomTom app will detect when you're close to a turn, tell you (out loud, even) and advance to the next step in the route.
I think the turn-by-turn technology (basically the ability to detect when you've completed a turn) is patented, so the Google Maps app does all it's really allowed to do without infringing patents (hence the need for you to tell it when you've completed a turn.) This also would explain why no turn-by-turn apps are allowed in the app store.
Thanks, slashdot, for swallowing my comment.
Meant to say: Both of these issues were fixed a long time ago. Get with it.