9/10    When and when isn't == equivalent to equals() in regard to Objects?
        \_ == is reference equality (true iff it is the same instance of the
           String s1 = "foo"; String s2 = "foo";
           object).  You can overload equals() to do anything you want,
           in principle; by convention, it is used to test whether the objects
           are semantically different.  Default implementation of equals()
           (in class Object) simply does reference comparison with ==.
           One common class that overloads equals() is String; it is not
           very intuitive when two Strings are == or !=.  See 3.10.5 of
       http://java.sun.com/docs/books/jls/second_edition/html/lexical.doc.html
           Compare Strings with equals() unless *both* Strings are intern()ed.
           Compare Objects with equals() if the method could be overloaded,
           doesn't matter otherwise.  If this all is too complicated,
           that's because Java is broken.  -- misha
           \_ yeah, perl is much better    -- troll
              \_ Fix your garbage collection. -- troll2
        \_
           String s1 = new String("foo"); String s2 = new String ("foo");
           String s1 = "foo"; String s2 = "foo";
           (s1.equals(s2))      //TRUE, because of String's 'equals' impl
           \_ Correct.
           (s1 == s2)           //FALSE, because they don't point at the
                                        same objects
           (thanks for the correction)
           \_ This is correct when s1 and s2 are assigned at
              runtime. If s1 and s2 are assigned to literals as above,
              the strings will be interned. So (s1 == s2) as you have
              it is true. But (s1 == "food".substring(0, 3)) is false
              because the substring call happens at runtime.