Comment by nicce
2 days ago
I would even argue that the current design of the bike line is better than the one suggested by the author.
It forces the biker to slow down and reduces the collision risks with others in the line.
It is selfish to think only about the biker coming from the hill. The biker that thinks it is okay to drive 20mph in that situation.
Yeah, that's why we put sharp turns at the bottom of roads too.
It is selfish to only think about the driver coming from the hill. The driver that thinks it is okay to drive 45mph in that situation.
Do you see the irony of your statement.
We put sharp turns at the end of roads.
If you have a high-speed road merging into a slow one without some indication that it's ending and a sharp turn at the end, you have a road that kills people.
You can accomplish both with the right design.
By not merging the cycling and walkway, sure. That would be a better design.
But presumably real world limitations forced them to merge the two at this point, and forcing cyclists to slow before the merge is of obvious benefit to the safety of pedestrians and cyclists. Not to mention that road construction crews can't fabricate an infinite array of curbs and affordances as a simple practical limitation.
As others have cited, the author seems to have an "everything is an easy fix" perspective to the world, at least when viewed as their own requirements and needs being the only consideration. In reality, loads of people care immensely about all the things that they think are easy fixes, but the fixes aren't nearly as easy as they think. Like, anyone who has ever listened to a user tell them how their app could be made much better knows this, when all of their suggestions would diminish usability for almost every other user.