@multithreading
At the risk of contributing to another pages-long angry debate about mutithreading, I would just like to add my two cents on the issue: (note: the following is just an opinion)
Specifically, unless you are running a small set of completely independent things, multithreading is a lot of work to get right, and in general forcing multithreading into problems that don't lend themselves easily to task division is dangerous, and overall just bad programming practice, because you can actually end up slowing your program down if the tasks aren't large/separable enough.
In general, wherever possible, a good programmer should try to improve their
algorithms, as opposed to relying on hardware growth as a crutch. If you don't believe me, take a look at the pathing costs in the algorithms compared
here. Typically, for similar amounts of effort, you'll make much greater gains by trying to compute things in a clever way than trying to multithread them. Only when you're certain that you've made all possible algorithmic improvements, and things are
still too slow should you start appealing to multithreading as a last resort.
@
BACK ON TOPIC:I am super excited about the opportunity to clothe my dwarves. I typically turn migration off early and run very long forts which have lots of children, all of whom invariably end up running around in the buff claiming every discarded sock on the ground but never doing anything with them, well into their adult years.
Not to mention any ulterior motives I might have for wanting to see dwarven clothing bugs fixed...