UI apps are a little different and are treated as multithreaded/multicore as often as possible There’s a management thread to handle UI (click/type/update) and background threads to handle long-running processes That’s how you get something like a little spinning wheel while things are working in the background It’s pretty easy to tell if an app is “sitting on the UI thread” since the window seems like it locks up for a bit For games, you may have multiple management threads – a UI thread, a physics thread, etcFor things like scripts, single thread is usually what you want except for tiny bits like aforementioned parallel encoding, parallel compiling, etc If it’s something that’s run on an infrequent basis, then it’s not even worth tuning Keeping it sequential actually ends up being better, because if something breaks, it’s easier to dissect and fix

Your blog has really piqued my interest on this topic. Feel free to drop by my website 46N about Thai-Massage.