Java will never have physical thread support in the language itself, because that would destroy system independency. But the JavaVMs usually map Java threads to "real" threads just fine (depending of what concept of "threads" the underlying OS and CPU architecture has). Java is really good at multithreading, it's usually the developers that suck and then just say "it's Java, what did you expect?" to cover up their mess. I'm pretty sure he added that feature to Minecraft itself, which obviously won't stop development just because CraftBukkit experiences performance issues that need to be fixed. What are you trying to prove here with such attacks?