Re:Long Answer? (Score 1)

If it wasn't a UI element we were talking about here you'd still have to deal with some manner of synchronization primitive, which could have potentially been disposed of already (event occured during app shutdown) or a wait timeout resulting in a condition that needs to be handled. I won't argue that there isn't some opportunity for excellence on the part of the framework/runtime here, but thread synchronization and communication of any sort is going to require more care on the part of the developer regardless of language, platform, or API. It's been many years (~13) since I've written code for NeXTStep..er..OSX but I don't recall this problem space being substantially easier to manage there.