[blasdel]

The problem is that they can't change the UI model without pissing off their existing userbase that likes clicking cardinal arrows to shift the map tiles around. Google's never going to implement that interface, even their nojs interface uses a different UI model.

If Mapquest's users wanted GMaps, they'd have switched by now. Aping that would only infuriate them, and since Google will always do a better job of implementing the rich JS interface than Mapquest can, the previously-recalcitrant users would just switch.

[danilocampos]

OP suggested this was happening back in the day. Either way:

MapQuest didn't suck because of its UI model. MapQuest sucked because it was clunky, slow, and cluttered. Its implementation was crap.

When you look at today's MapQuest, they've largely corrected this. The maps are much less ugly, they now pick a (somewhat) reasonable level of detail based on your zoom level and moving around the map is fast whether you're using their joystick control or dragging the map.

The sad thing is, none of this is rocket science. It shouldn't have taken them this long to figure out. Google Maps steadily, inevitably eroded their market share and last I heard, they were 10% behind.

[WalterBright]

I stopped using MapQuest because I got tired of the errors in it - locations were often a mile or more away from where MapQuest said they were, leaving me driving around in circles.