|
|
|
|
|
by SahAssar
2805 days ago
|
|
A subway is a high latency, high bandwidth carrier. A bike track is a low latency, high bandwidth carrier. That is in a subway all "packets" (people) need to wait for the next opportunity to depart, whereas in a bike system all packets move more slowly, but at a more continuous pace (set by the maximum speed of the transport). A lot more people can pass any point in a biketrack per hour than they can per subwaytrack, and they can often take a more direct path to their destination using bikes than they can by subway. That also means that a bike system is better suited to a city where both the departure and the destination are diverse among all "packets". That's not even starting to talk about how biketracks scale much better economically since they are much cheaper to build. |
|
Trains coming in each couple minutes - show me lower latency than that :)
>A lot more people can pass any point in a biketrack per hour than they can per subwaytrack
several hundreds (up to a thousand in rush hour packing) people per train each couple of minutes - beat that.
Anyway, the rest of what you're saying about biking is just a theory that doesn't come even close to the reality of any big dense city in Europe/Asia. This is why those cities has highly developed subway system - the low latency high bandwidth and high speed mode of transportation. You put all these people on bikes and they would choke the city.