We're talking about a car, not a mobile phone. It's a 3000-pound chunk of metal that moves fast enough to kill anyone who comes into contact with it, and sometimes even those who ride in it. The ability to consult with a remote server would be nice, but the car should perform just as well even when a neighborhood prankster jams the cell & GPS signals.
So the entire approach of relying on a map might be misguided, regardless of whether the map is precompiled or JIT-crowdsourced. It seems that the current generation of autonomous vehicles rely too much on maps and too little on situational awareness. The next generation will need to make a lot of advances on the latter. Ideally, a car should be able to make all millisecond-by-millisecond decisions by itself, offline if necessary, and use the map only as a hint.
What I liked in this article is that it reveals to the public that google's communication on the topic is really skewed. They try to make people think that the problem of autonomous driving is basically solved while many big challenges remain.
The cars at this early stage require everything to be meticulously mapped, but I'm sure Google are working hard on making them handle unmapped situations as well. They have a lot of sensors; surely at some point they can start relying on them for unmapped situations.
If the car was able to do that simply by slowing down you wouldn't need the map in the first place.
The whole point is that a human needs to map it. The car has no idea what to do.
For example it doesn't "see" a stop sign and act on it. It knows in advance there is a stop sign there because a human told it so.
It's not scanning the environment looking for traffic signs, all it's doing is looking for obstacles in the way and avoiding them.
It doesn't even see the road edge, or the lane markings - it knows that in advance.
Things are way worse for all kinds of changes to roads. Even if the first car correctly classifies that white spot on the road as a lost paper that it can drive over, what good does that do the next car? The wind may have blown it away or to a different location and into a different shape.
To me, Google's approach seems an attempt to build a model of what the entire world looked like a short while ago, while cars only need a rough model of what it looks like now.
Scaling Google's approach to millions of cameras in million of cars may improve the model and decrease its latency and might make the latency low enough, but I don't see why it would be the best approach.
There are a tremendous number of things to map. If they could all be understood automatically google wouldn't need to map them ahead of time.
If you think about it, it's a really fun problem to get to solve, wish I was working on it.