A good amount of the latency associated with DSL has to do with the quality of the last mile link. There are two different modes that DSL can operate in, Interleaved and Fastpath. Interleaved tends to add another 20 or so ms to the first hop (and thus everything else). Cable doesn't have the same difference; if it works the latency to the first hop will be the same.
That said, my Comcast link and Fastpath DSL service from AT&T have very similar latency to Chicago. I don't know where you're located but from East Lansing MI:
Tracing route to vnsc-bak.sys.gtei.net [4.2.2.2]
over a maximum of 30 hops:
1 7 ms 6 ms 7 ms adsl-108-68-143-254.dsl.lgtpmi.sbcglobal.net [10
8.68.143.254]
2 7 ms 7 ms 7 ms dist2-vlan52.lgtpmi.sbcglobal.net [70.226.51.34]
3 7 ms 7 ms 8 ms bb2-gi8-0-1.lgtpmi.sbcglobal.net [151.164.100.83
]
4 13 ms 13 ms 13 ms ppp-151-164-55-178.eulstx.swbell.net [151.164.55
.178]
5 31 ms 36 ms 71 ms xe-11-2-0.edge4.Chicago3.Level3.net [4.68.62.41]
6 31 ms 31 ms 31 ms vlan51.ebr1.Chicago2.Level3.net [4.69.138.158]
7 34 ms 62 ms 34 ms ae-5-5.ebr2.Chicago1.Level3.net [4.69.140.193]
8 34 ms 44 ms 32 ms ae-11-51.car1.Chicago1.Level3.net [4.68.101.2]
9 33 ms 32 ms 32 ms vnsc-bak.sys.gtei.net [4.2.2.2]
Trace complete.
Tracing route to vnsc-bak.sys.gtei.net [4.2.2.2]
over a maximum of 30 hops:
1 23 ms 28 ms 28 ms 71.238.248.1
2 7 ms 8 ms 8 ms te-9-3-ur02.holt.mi.michigan.comcast.net [68.85.
48.117]
3 14 ms 13 ms 19 ms be-30-ar01.pontiac.mi.michigan.comcast.net [68.8
6.140.69]
4 26 ms 27 ms 25 ms pos-3-3-0-0-cr01.chicago.il.ibone.comcast.net [6
8.86.90.109]
5 26 ms 25 ms 27 ms xe-10-1-0.edge1.Chicago2.Level3.net [4.71.248.17
]
6 40 ms 46 ms 35 ms vlan51.ebr1.Chicago2.Level3.net [4.69.138.158]
7 68 ms 35 ms 34 ms ae-6-6.ebr1.Chicago1.Level3.net [4.69.140.189]
8 28 ms 27 ms 40 ms ae-11-51.car1.Chicago1.Level3.net [4.68.101.2]
9 28 ms 27 ms 30 ms vnsc-bak.sys.gtei.net [4.2.2.2]
Trace complete.
Only way to really know, try the service.
