I fail to see how is that relevant in their solution, but you also used it in your own solution.

Not only the local StringBuilder instance doesn't leave the scope of the method, they don't even create threads in their solution to worry about this.

However, concatenation operation AFAIK creates StringBuilder instances each time they are called on two String instances, and return StringBuilder.toString().

It's not thread safe