> Google doesn't seem to count the time of waiting for the next subway train.Pretty sure it does. My understanding is that it computes the time simply as (estimated_end_time - start_time), and it determines the estimated_end_time as whenever you would reach your destination, which accounts for train schedules and walking time.
> Since most people probably won't cut it that close...
At least in NYC, IME people did cut it that close because during regular hours (that actually extend pretty late into the evening) the frequency is high enough that if you miss a train you only need to wait a few minutes for the next one.
The other thing that has not been mentioned so far in this sub-thread (but maybe elsewhere) is that public transport is very relaxing. Even if it's crowded and you have to stand, you can use your smartphone because there is wireless reception on the subway.
And if you consider the madness that is driving in NYC traffic, there is no comparison. It's maddening even just sitting in a rideshare. I'm surprised you're seeing driving times being comparable. I'm actually doubting the Google Maps estimates, which are usually rock solid.