But I agree with the parent, the suite of driver assistance features is very good, but a long way from "self driving".
107 karma · joined November 19, 2009
[ my public key: https://keybase.io/scotje; my proof: https://keybase.io/scotje/sigs/Rc3Se-62OMw19wbI_qhFhRt4CaRPEwXTe-Kd227eqfI ]
But I agree with the parent, the suite of driver assistance features is very good, but a long way from "self driving".
We actually tried something pretty similar last year here in Portland (the site is still alive at www.localplate.com although we have ceased operations), we found it pretty challenging just to get people to plan ahead far enough for our offering to be viable. (We came across some consumer research that something like 70% of households don't have a plan for dinner until sometime the same day.)
We eventually tried distribution through existing retail channels which definitely helped with the traction side but made the economics pretty challenging. :)
Best of luck though, it's an interesting space with a lot of people attacking it from different directions right now.
(E-mail is in my profile if you want to know any more about our experience.)
But a did find a nice picture of the reactor pit: http://3.bp.blogspot.com/-jYVl__lRp5s/Tfpf4Cyi6rI/AAAAAAAAA6...
Still looking for what would apply to the Navy reactors.
http://manhattanprojectbreactor.hanford.gov/
I've gone twice and it is really fascinating. You get to stand about twenty feet from the face of the reactor core, walk around the control room, etc. I have some pictures and video I can share if anyone is interested, although I'm sure some Googling can turn up lots of them as well.
One of my favorite anecdotes is that the valve covers for all the cooling pipes are open and have to remain that way so that the Russian inspectors can verify each year that there is no evidence that the reactor has been in operation. (Not sure if these inspections are actually still happening.)
Also for arms control purposes, there is an open pit elsewhere on the site where decommissioned US Navy reactors are stored. (Russia can monitor the number and position of them via satellite.)
(Looks good now that I have the right release deployed, by the way.)
The reason I went with "vendor everything" several years ago was that I had to make some changes to a legacy codebase and discovered that one of the gems it depended on was no longer available. It wasn't the end of the world to refactor around it, but it motivated me to find a way to ensure I would always have a local copy of all the dependencies for each app.
Someone in the comments of the rubygems.org story yesterday mentioned using a submodule for vendor/cache which seems like an interesting idea to me. That could at least partially address #3.
I generally try to follow the "vendor everything" philosophy: http://ryan.mcgeary.org/2011/02/09/vendor-everything-still-a...
Maybe just get rid of that pricing line in the comparison?
They placed a bet on their car and it didn't pay off. Doesn't mean it was a bad bet. (In fact, since it sounds like they were the consensus favorites going into the competition, it was probably a good bet.)
http://store.apple.com/Catalog/US/Images/salespolicies.html#...
Edit: Here's a pertinent quote from that article...
"So, an entire day and more than a quarter tank of gas later, here are the results. Holding the iPhone 4 without a case, in your left hand, crossing the black strip can result in a worst case drop of 24 dB in signal. As we'll show in a second, how you hold the phone makes a huge difference across every smartphone - and we've tested thoroughly in 5 different positions.
Now, there are two vastly different possibilities for what happens to the bar visualization after you drop 24 dB. I happen to live less than one block from an AT&T UMTS tower (it's across the street, literally), and have exceptionally strong signal in all of my house - it's part of why I chose to live here, actually. Signal is above -65 dBm in every single room, in most cases it's at -51 dBm. When I incur that worst case drop of 24 dB from squeezing the phone, I fall down to -83 dBm, which is still visualized as 5 bars.
However, in locales that have less signal, but where iOS still displays 5 bars, the drop of 24 dB is visualized much differently. For example, at another test location, signal without holding the phone is -89 dBm, which is still displayed as 5 bars. Cup the phone, and you'll fall all the way to -113 dBm. All the bars dramatically disappear one after the other, people think they've dramatically lost all the signal, and you know the rest."