XyzWs Java FAQ: What are the difference between String, StringBuffer, and StringBuilder?
What are the difference between String, StringBuffer, and StringBuilder?
The String class is immutable, however StringBuffer and StringBuilder classes
are not immutable. There's no reason to use a StringBuffer or StringBuilder
unless you're planing on changing the contents.
The String class overrides the default equals() method, but
StringBuffer and StringBuilder do not override the default equals()
method in Object class. The equals method for class Object
implements the most discriminating possible equivalence relation on objects;
that is, for any non-null reference values x and y,
this method returns true if and only if x and y
refer to the same object (x == y has the value true).
For example,
public class Program {
public static void main(String [] args) {
String s1 = new String("Hello World");
String s2 = new String("Hello World");
System.out.println("s1.equals(s2):" + s1.equals(s2));
StringBuffer sb1 = new StringBuffer("Hello World");
StringBuffer sb2 = new StringBuffer("Hello World");
System.out.println("sb1.equals(sb2):" + sb1.equals(sb2));
StringBuilder sd1 = new StringBuilder("Hello World");
StringBuilder sd2 = new StringBuilder("Hello World");
System.out.println("sd1.equals(sd2):" + sd1.equals(sd2));
}
}
A StringBuffer class implements a mutable sequence of characters. A StringBuffer class is like a String, but can be modified. At any point in time it contains some particular sequence of characters, but the length and content of the sequence can be changed through certain method calls.
String buffers are safe for use by multiple threads. The methods are synchronized where necessary so that all the operations on any particular instance behave as if they occur in some serial order that is consistent with the order of the method calls made by each of the individual threads involved.
The StringBuilder class provides an API compatible with StringBuffer, but with
no guarantee of synchronization. The StringBuilder class is designed for use as
a drop-in replacement for StringBuffer in places where the string buffer was
being used by a single thread (as is generally the case). Where possible, it is
recommended that this class be used in preference to StringBuffer as it will be
faster under most implementations.