4 ms·

Async didn't change anything for you? It seems pretty big to us.

• manojlds 12y ago
  My main thrust was that the last release was 2 years ago, and relatively, the changes in 5.0 were minimal. (async-await is nothing compared to changes in 3.0 and 4.0)
• S_A_P 12y ago
  I think Async was not very big for big legacy code bases. I have used it a handful of times, but it had nowhere near the same impact as Linq and lambdas had on my daily activities. In fact I would say that has had the single greatest impact on my coding style and habits...
• ryanjshaw 12y ago
  I used async for a WPF application. That worked out well. I also experimented with a scraper using async. I dug myself into holes very quickly (memory usage ballooned, difficult to debug and reason about application state despite the code being very easy to read, threads were being created all over the place which annoyed me even though I understood why). I rewrote the scraper to use BlockingCollections and Take(), with async being used solely with the HttpClient (which really needs to learn how to play nicer with async in the face of network errors!). The code was more decoupled, and while slightly more difficult to follow because of this, far easier to test and debug because the working set of my application was explicit rather than hidden in tasks. This had the added benefit of making it easy to persist and restore state. For me, the concurrent collections introduced in .NET 4 have been the big winner (no more custom thread pools!). Use of async needs to be matched carefully with the problem domain, especially in backend development.