Or, as I started this topic:
As Junilu pointed out in his very helpful answer, this is equivalent to declaring an anonymous Runnable. Even if I had declared an explicit Runnable, I'd still have to spin up a thread to run it.
And yes, I do know about Futures and Callables and ThreadPoolExecutors. But that wasn't the question I asked. I have looked at the web trying to get an answer to the Thread vs Runnable question, and despite special pleading for Runnables as "preserving the option to inherit from other than class Thread", and "Runnables can be reused" there are lots of times when these just aren't an issue. As far as I can tell, it boils down to personal preference.