|
|
|
|
|
by q845712
1188 days ago
|
|
imo there's already a bunch of inconsistent nanny-state stuff when trying to use a smartphone as a passenger/navigator. There's things I'm not allowed to do without unplugging the phone briefly, and there's also things I'm allowed to do that absolutely require looking down at a zero-haptic-feedback touchscreen. It seems like there's always corner cases that aren't considered (in your proposal above, what if the navigator doesn't have a phone because they're a child, or because their phone ran out of batteries? What happens when the sensors/algorithms are wrong about how fast we're going? What happens when the sensors are wrong about whether or not there's another device? What if that second device keeps disappearing and re-apparing while somebody tries to do a multiple step operation?) ... Trying to build some water-tight mechanism to keep us out of trouble but also with access to full functionality "when we can use it responsibly" is an endless rabbit hole. IMO it feels like a systemic problem asking for a systemic solution. Whether we think that solution is self-driving cars, rail travel, walkable cities, or taxis probably says as much about our politics as anything else though. |
|