This week's book giveaway is in the Mac OS forum. We're giving away four copies of a choice of "Take Control of Upgrading to Yosemite" or "Take Control of Automating Your Mac" and have Joe Kissell on-line! See this thread for details.
The super keyword which allows one to access the superclass object [or maybe that part of the object which is inherited unchanged from the superclass] is directional. A subclass "knows" which superclass it inherits from. When you writeorthe subclass knows to look in Foo for its superclass implementation and in Bar Barbar and Barbarbar for its interfaces. Remember super always refers to what follows extends.
But there might be several classes which extend Foo, and several which implement Bar Barbar and Barbaranne. If you had a "sub" keyword, it would not "know" which subclass to look for. Even javadoc can only find "direct known subclasses" (look at non-final classes in the API specification and it says that quite often), not "all direct subclasses."
A subclass might also have additional fields which are not in the superclass; there is no way the superclass could "know about" them.
It would not work having a "sub" keyword. I hope I have explained why so you can understand it.
subject: Accessing overridden methods with supoerclss ref variable