> One should always prefer the Axes way of doing it, it's refactorable and uses less hidden global state. I fully agree, but half the time you're looking up ho

> One should always prefer the Axes way of doing it, it's refactorable and uses less hidden global state. I fully agree, but half the time you're looking up how to do something, you find methods documented using the other approach, with slightly different method names that don't even have an alias in the axes API. In fact those are usually the ones you find, because people answering SO questions seem to prefer the brevity.