Anyone who has spent any time on a 1G Ethernet network understands it.
Let's take http://maps.Goggle.com as an example.
When you "click and drag" the map around, the adjacent part of the picture loads so fast in a cable connection that it's almost like it was on your hard drive, in other words latency is less than ~50 ms.
This is no big deal today, each little image is not that big, and it is transfered so fast and reliably that it's taken for granted by the user. The Telco and not google, has delivered latency so low that it makes their "application" run fast, and google makes a lot of money from it.
If every time you clicked and dragged you got a flickering add-vert from SBC, you'd know who was delivering the content.
As we scale from Meg to Gig to Peta speeds, the value of latency in the software development world goes up.
If the telco was smart, they would edit the google HTML on the fly and insert their own advert into every other frame of the redraw for 0.01 second and then start negotiations for it's removal.
I have just as fast of an Intenet experience with my DSL line from Verizon as do all of my neighbors with cable modems and any of my friends in the NYC metro area with cable modems (I've tested all of them).
It is my experience that the touted distinctions in speed between cable modems and DSL is a distinction without a practical difference.
The only faster experience I ever had is with an Internet connection achieved by a fiber-optic cable and router system connecting to a fiber-optic intranet backbone on the campus of Columbia University. Their campus backbone has a direct fiber-optic connection to the Internt through servers run by NYSERNET - New York State Education and Research Network. NYSERNET built and operates the lower NY state primary segment of the Internet on massive servers in the Columbia School of Engineering. That operation was established in 1987 and was upgraded many times since then. It was more like "sitting" on the Internet than "connecting" to it.