StringBuffer is obsolete?

Question

In the book \"Effective Java\", Josh Bloch says that

StringBuffer is largely obsolete and should be replaced by the non-synchronized implementation \'S

Answer 1

Not everyone reads as widely as you :-)

I'm only half-joking. People copy code and patterns all the time. Many people don't stay in touch with API changes.

Why is StringBuffer obsolete? Because in the vast majority of cases, its synchronised behaviour isn't required. I can't think of a time I've ever needed it. Despite the fact that synchronisation is not now the performance issue it once was, it makes little sense to pay that tax in scenarios where it's unnecessary.