2 ms·
Yes they are on the whole. But that one time there was some unexpected delay, and it ruins any goodwill the clock built up in the eyes of the rider. It's quite
by Tokkemon 7y ago
Yes they are on the whole. But that one time there was some unexpected delay, and it ruins any goodwill the clock built up in the eyes of the rider. It's quite frustrating to see.
- jrockway 7y agoI have seen them wrong, it didn't ruin the goodwill. What I take away from the clocks are minor delays that don't get mentioned in the official notifications. I often see arrival times like "1 3 15 21" (literally a sample taken right now for my home station) and know something is wrong, but there is no communication from the MTA about it. I then choose an alternate route. What the MTA needs to fix is when the schedule says that trains run every 3 minutes, the countdown clock needs to look like "1 4 7 10", not "1 4 33 36".
- notyourday 7y agoThe purpose of the countdown clock is to provide information about that "unexpected delay". The clock is irrelevant if the trains are arriving every 3-4 minutes. Think of this being an autoscaling group. The argument that people make sounds like "Well, autoscaling group works fine when one instance can handle all the traffic. We are happy with it." It is not an achievement to have an autoscaling group work when it has one instance in it.