Slashdot videos: Now with more Slashdot!
We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).
Disappointing that the Star Trek tie-in was mentioned but the link was omitted...
Not necessarily. A larger car can have bigger crumple zones. If its crumple zones are twice the size of the small car, then the acceleration that you'll experience in the collision is a lot less and so there's a greater chance everyone will survive (assuming that the relative impact speeds will be the same).
Don't let facts get in the way of a good story.
Armed with this information an autonomous vehicle trying to protect everybody should: (a) choose the impact with the least inertia for all concerned (i.e.: go for the car travelling in almost the same direction as the autonomous vehicle as opposed a car travelling in an opposite direction) and (b) for a choice of head-on impacts, prioritize impacting the car with a mass closest to its own. An autonomous vehicle biased towards protecting its own driver should target the smaller vehicle... but this will inevitably lead to "I've got the biggest autonomous vehicle" wars with people trying to protect themselves from other vehicles as we've seen happen with SUVs.
"Stop using your ISP's DNS" is not always the right answer.
If I use Google's public DNS servers it breaks content distribution networks like Akamai. For example, if I use Google Public DNS then *.phobos.apple.com addresses for iOS and OSX updates resolve to IPs inside NTT (Tokyo, Japan) and downloads are exceedingly slow (high latency, dropped packets, etc.). If I use my ISP's DNS server it just so happens they host a set of Akamai nodes and the *.phobos.apple.com addresses will resolve to IPs only 2 or 3 hops away, so downloads will saturate my SDSL connection.
Comcast should just acknowledge that they've fucked up and fix their servers.
Yeah, describing it as "handheld" is kind of misleading. The photo in TFA shows *just* the handheld part, there's a much larger piece of equipment attached via cable and worn backpack-style...
Should Jade Rabbit make a full recovery, it would cap another success for space exploration, which has seen NASA's Opportunity Mars rover, currently exploring the red planet, far outlast its expected lifespan."
Opportunity far outlived its projected 90 day operational lifetime. Jade Rabbit was supposed to go 3 months and has already gone belly-up just a month into it.
Or if you're me, the worst phone you could ever imagine (battery life, robustness, size, speech quality, too many button presses until i can do what i want to achieve).
I see you've never owned a Motorola RAZR then.
The scaly texture conceals small holes in the material where water is sucked in.
I think the
Put a hardware driver author in front of a documentation pack and a compiler, and tell him to write a driver, and he'll tell you to fuck off.
My how things have changed. I remember being handed register documentation for StarPort 16-, 32- and 64-port serial cards and being asked to write FOSSIL drivers for them. And I had to supply my own compiler and logic analyser.