Here's a thought - maybe TaskGroup itself should also be deprecated. I'm wondering if it might encourage bad development practice. While it allows you to execute multiple tasks in the background, it doesn't "return" until all of those tasks are complete. One might argue that a well-designed UI should present information as soon as it becomes available.
For example, let's say you are writing an app that browses a product catalog. You create one task to pull a product image from an image server, another that retrieves a product description from a database, and a third that pulls pricing and inventory information from another back-end system. TaskGroup allows you to wait until all of that data has been retrieved before presenting any of it, but is that really the best user experience? Maybe not. There may be valid use cases for something like this, but I'm just wondering if it is common enough that a class to facilitate it should be included in the platform. The lack of a dedicated TaskGroup class does not preclude a developer from implementing similar behavior at the application level. G
