Thought I would start this thread as a way of explaining why I like PathPilot over the standard Axis interface, Gmoccapy and others.
In one word, usability. Coming from the Mach world where screens are alot prettier (and sometimes way uglier) PathPilot presented a really user friendly interface. One thing I really like is the ability to jog my machine while any of the screens are active. The only thing I can't jog within is the MDI line. Why do I like this? My machine is 2400x1200 and when you need to sight X0Y0 somewhere within the table, working from the computer is not feasible. I don't have to worry if the interface is on the main screen, the conversational screen, the offset screen or anything else (apart from the MDI line), I just take my wireless keyboard, plunk it down on the machine and jog to where I want.
Another thing is some idiot proofing. For example, touching off to set Z zero. If you forget to set the search speed to slow PathPilot will set it to a slow default speed automatically before the cutter takes off at 5400mm/pm or whatever speed was last used.
However there are things I don't like, like being limited to having my config files be in imperial settings. I did try to set things like scale in metric but that threw out all sorts of things within PathPilot as, for metric, they convert everything on the fly depending if G21 is set by the incoming gcode.
Now if I could have PathPilot's pretty face on a standard LinuxCNC install where I could easily replace parts, like cutter touchoff and toolchange, I would be a really happy man.
Now I must say that at this moment I have returned to Axis due to problems with my PathPilot install but would return to it in the blink of an eye if could get it working again, too damn nice to let go!
So, why do others want PathPilot over the usual LinuxCNC interfaces?
.... just kidding 
