(I don't want to go to deep but have a look at Moravec's paradox if you are really bored).
Although I'd not heard of it until you mentioned it, there was a great example of Moravec's paradox in the Darpa Robotics Challenge
http://www.theroboticschallenge.org/ which was held over Friday/Saturday this week. In it, robots had to drive a (modified) jeep, get out, open a door, turn a valve, pick up a power saw and cut a hole in plasterboard (around a guide), unplug a cable and plug it into a different socket, clamber over (or shove through) some "debris" and climb 5 stairs.
The whole event was streamed live, and it was fascinating viewing, even though a lot of the time there was so little action that it was like watching paint dry. Three robots took home prizes, and all 3 managed to complete all 8 tasks within an hour (there were another 21 teams that achieved 7 or fewer tasks). I'm guessing any average human could have finished the course in 2 minutes max - and without needing a team of engineers to send commands, pick them up when they fell over
https://www.youtube.com/watch?v=7A_QPGcjrh0 (10 minute penalty applied) etc. etc.
Over time the robots are only going to get better and better, but because the real world's full of awkward things like gravity, wind, rain, sharp angles, unstable surfaces, etc. etc. it's probably something where improvement will be relatively slow.
On the other hand, the Darpa self-driving car challenge
http://en.wikipedia.org/wiki/DARPA_Grand_Challenge started off amazingly badly in 2004 but then technology advanced very quickly in subsequent years of the competition, and led to spin-offs like Google's autonomous vehicles which have driven over 1,000,000 miles without any computer-caused accidents.
What's the difference? Well, trying to get a bi-pedal(ish) robot to walk through a simulated urban environment is incredibly hard because it requires the equivalent of fine motor skills - but getting a car to drive itself safely is very much a brute-force computation exercise. The car's in no danger of falling over, so the actual physics behind its movement are very very simple compared to trying to keep a robot balanced as it walks and navigates obstacles, climbs stairs etc. The "big ask" is the ability to see/interpret the road ahead, and to analyse and respond to hazards/dangers/situations - all things that improve very quickly as you throw more computing power at the problem.