This probably already has been discussed somewhere, but can someone point me at or tell me what's the reasoning behind copying the same names for Task.Priority from other Apple API's other than precedence? Not every application has UI involved, yet the naming scheme still uses that convention. If there is still room for improvement, I would personally love a new more generic set of names. The frameworks that need a 1 to 1 conversion can provide a non-failable initializer on appropriate types. Dispatch framework originated at Apple but was made available for other platforms, so there was no room for changing the names. However Task a brand new API which is meant to be a general purpose API, so why do want to re-use the naming convention from a framework which was based around UI?
20 Likes