Here's a counterargument for this, just to be a fuddy-duddy: One of the key activities in programming is reasoning about time and space cost, and this is a spa

Here's a counterargument for this, just to be a fuddy-duddy: One of the key activities in programming is reasoning about time and space cost, and this is a space optimization that's nondeterministic. It kicks in sometimes, or sometimes not at all, and happens behind the scenes at garbage collection time when it's nearly invisible. If you're sloppy, your program may have a huge asymptotic space usage, and this may paper over it. But the impl has heuristics, it may not work all the time -- even their example program needed Thread.sleep() calls! Unpredictable semantics help nobody. So I always liked explicit string interning (whatup, Lisp!). All the same, faster is better and I'm sure this makes things faster. Oh and can we talk about how broken it was that Java 6 and under had a fixed size pool for .intern()'d strings?