In my 10 years of experience writing in a language that I like and I think I know rather well, I cannot share your view that “async/await is easy”. The happy path is easy, but you’ll hit show-stopping issues when you’re building big complex systems.
1,113 karma · joined July 23, 2013
In my 10 years of experience writing in a language that I like and I think I know rather well, I cannot share your view that “async/await is easy”. The happy path is easy, but you’ll hit show-stopping issues when you’re building big complex systems.
That won’t work with various synchronization contexts, where doing this would cause a deadlock. There’s not much fun in trying to debug such issues.
And now that various libraries only provide async api, or worse an non-async version wrapping the async one with . GetAwaiter().GetResult(), you’ll be in for a treat updating your dependencies.
Async all the way is the answer, although various frameworks still don’t offer async hooks. Recently I ran into this for example trying to write an async validator in blazor, but that’s not possible and you have to work around it [1].
C# 5 introduced async/await almost 12 years ago. And we’re still not “async all the way”.
The screen you referenced would be even less than that at 2x scaling factor: 1920x900, which is even fewer screen estate. A 4k ultrawide is not retina, so doesn’t cut it.
> [08:00 UTC] Current Status: The impact has been mitigated for most regions, except for West Europe. Customers should observe the recovery of services in the affected areas. Further updates will be provided as the situation progresses.
Over 6 hours now in 'my' region. Can confirm that seemingly nothing really works in the portal.
While understandable from his POV, I'm disappointed to see the guy getting paid for services not rendered, and so reinforcing his tactics.