There also aren't that many things to do with your life once you're out of school that don't involve the bottom half of the bell curve. Being able to work with a wide range of people is a huge asset to anyone.
Intellectually bright kids who struggle socially are often told that it'll be better once they get to the next level: don't worry so much about grade school, it'll get better once you get to middle school. Don't worry so much about high school, it'll be better once you're in college. And the greater freedom at each level does help, but no one will ever tell you that the politicking, the popularity contests and the pettiness don't go away at all in the working world. Figuring that stuff out at a young age with less severe consequences for mistakes is the best thing a kid can do for their long term success.
There isn't one answer for either desktop or server workloads, only trends. Some processor resources get cut in half between threads, some are duplicated and the threads compete for some others. If your favorite benchmark bottlenecks on a resource that's shared or divided between threads, it'll probably do worse with hyperthreading on; if that's not the case, and a lot of the instructions in the hot path can go to any decoder or ALU, it'll probably do better.
Intellectually bright kids who struggle socially are often told that it'll be better once they get to the next level: don't worry so much about grade school, it'll get better once you get to middle school. Don't worry so much about high school, it'll be better once you're in college. And the greater freedom at each level does help, but no one will ever tell you that the politicking, the popularity contests and the pettiness don't go away at all in the working world. Figuring that stuff out at a young age with less severe consequences for mistakes is the best thing a kid can do for their long term success.