News for hackers. Stuff that matters.
Re:Uber is moving its self-driving cars from San Francisco t... by fabian2k on Thursday December 22, 2016 @04:42PM (#13240640)
Uber's almost pathological aversion to any form of regulation doesn't inspire confidence. The requirements in this case seem very reasonable, detailed accident disclosure is a reasonable thing to ask in my opinion.

My impression, based on this and other cases where Uber got in conflict with local regulations is that they don't seem to care whether the regulations are reasonable or not. They try to ignore them in every case.

Re:Uber is moving its self-driving cars from San Francisco t... by JumpCrisscross on Thursday December 22, 2016 @04:49PM (#13240673)
> They try to ignore them in every case

Other than for PR, I couldn't understand why Uber started testing in San Francisco. It's a densely-populated and heavily-regulated city in a heavily-regulated state.

Re:Uber is moving its self-driving cars from San Francisco t... by dragonwriter on Thursday December 22, 2016 @06:03PM (#13241198)
So, what you are saying is that SF is fairly representative of the kind of places with high demand for on-demand transit and high cost of human labor where automated taxis make the most sense.

Which, aside from convenience to Uber HQ, might explain why they'd want to prove the technology there.

Re:Uber is moving its self-driving cars from San Francisco t... by tyre on Thursday December 22, 2016 @05:39PM (#13241031)
Because that's where they are headquartered
Re:Uber is moving its self-driving cars from San Francisco t... by jayjay71 on Thursday December 22, 2016 @05:45PM (#13241080)
Yeah, I'm thinking a lot of the engineers will be unhappy about constantly traveling (or worse, moving) to Arizona.

Their self-driving engineers are now split among three locations: San Francisco, Pittsburgh, and Arizona. I think that alone is going to cause significant engineering friction. It's a lot harder to do remote work for testing live robots (especially if they can kill people).

Re:Uber is moving its self-driving cars from San Francisco t... by tyre on Thursday December 22, 2016 @05:51PM (#13241110)
I'm guessing it'll be worse than a centralized team, but not too bad.

The Pittsburgh team is there because of Carnegie Mellon, so likely where the hardware gets made. The software engineers in SF just need data from vehicles, which doesn't require cars to be near them. The operations folks actually going out and testing the cars can be anywhere, as long as they can stream data back to the SW and HW folks.

Re:Uber is moving its self-driving cars from San Francisco t... by Hydraulix989 on Thursday December 22, 2016 @07:46PM (#13241872)
The software engineers in SF are mostly doing data science-y type work or working on UberEATS.

The self-driving car ML software is also being worked on in Pittsburgh, along with the hardware.

Re:Uber is moving its self-driving cars from San Francisco t... by jayjay71 on Thursday December 22, 2016 @11:26PM (#13242820)
Most of the Otto engineers are still in San Francisco, and many of them are working on self-driving cars (in addition to trucks).
Re:Uber is moving its self-driving cars from San Francisco t... by Hydraulix989 on Friday December 23, 2016 @03:05PM (#13246918)
Oh yeah, I forgot about those guys. I do wonder what the dynamic is like between those two groups now...
Re:Uber is moving its self-driving cars from San Francisco t... by chinathrow on Thursday December 22, 2016 @05:56PM (#13241150)
Also because there are a lot of edge cases in SF.
Re:Uber is moving its self-driving cars from San Francisco t... by Hydraulix989 on Thursday December 22, 2016 @07:37PM (#13241830)
Take any edge cases in SF and multiply them by 10, and you get Pittsburgh.

Source: I grew up in Pittsburgh, and now have lived in SF since graduation.

Re:Uber is moving its self-driving cars from San Francisco t... by jaypaulynice on Thursday December 22, 2016 @05:37PM (#13241021)
Travis Kalanick gave a really nice TED talk about this: http://www.ted.com/talks/travis_kalanick_uber_s_plan_to_get_...