(Replying to PARENT post)
At least in SF, stop signs are proper optional. I see cars running them every day. It's just that when you see a car go 40 mph (5 over) and then slow down to 10 mph when it goes through it looks like it nearly stopped. When a cyclist goes from 15 mph to 10 mph it looks like he didn't do shit.
When I bicycle I stop fully at stop signs because I do it partly for exercise and I like practising the track stand, but I see people go through every day on my commute. If I were to bike in a hurry, I could see myself doing the slow down and treat-stop-as-yield.
Mostly there's a lot of bullshit on this topic, I've noticed. Somehow if you talk to drivers, they'll say things like "SF drivers don't know how to drive. They won't even see you before they go through a stop sign." then when the topic becomes cyclists v. drivers the narrative changes to how drivers turn into ever-correct rule followers. That seems to me that people are making an in-group v out-group distinction when they describe this, and appropriately changing their language.
I've got to tell you, I've seen it, and this "approximate the effect of a complete stop" is bullshit. Well, don't believe me, watch the video or wait at a busy trafficked intersection. (You can find good ones on the streets off Lincoln in the Sunset - heavily stop-signed and frequently violated)
(Replying to PARENT post)
By contrast, 5β10 miles/hour on a bike is about equally far from 0 and the 15 miles/hour the bike was traveling before.
The biggest difference though is that getting hit by a car doing a rolling stop will put you in the hospital and possibly kill you.
(Replying to PARENT post)
Rolling stops in cars still tend to approximate the effect of a complete stop. Rolling stops on bikes tend to approximate the effect of the stop sign not being there at all. It's two different cost/benefit situations producing two different outcomes.