Some of these things about async/await aren't all that obvious and different understanding of how to use it likely changed over time. The people that probably wrote the example code probably had it based on old information.
One of the things that gets me still with the async/await pattern is whether I need to call ConfigureAwait(false) or not - there seems to be a lot of different opinions about it online from a variety of people smarter than me.
C# is moving a bit fast that I feel sometimes it's burdensome to catch up with their latest updates.
I feel the same way about JavaScript!
As much as some of the new features that are being released (in JS, C#, CSS etc) are helpful and solves certain problems, there are some cases where I just look at it and wonder how we got here as it doesn't look easier/better than what existed.
No problem 🙂
Some of these things about async/await aren't all that obvious and different understanding of how to use it likely changed over time. The people that probably wrote the example code probably had it based on old information.
One of the things that gets me still with the async/await pattern is whether I need to call
ConfigureAwait(false)or not - there seems to be a lot of different opinions about it online from a variety of people smarter than me.Yeah, I still remember the first days I was cluelessly reading different articles about async C# and mixing new code with old one :D
C# is moving a bit fast that I feel sometimes it's burdensome to catch up with their latest updates.
I feel the same way about JavaScript!
As much as some of the new features that are being released (in JS, C#, CSS etc) are helpful and solves certain problems, there are some cases where I just look at it and wonder how we got here as it doesn't look easier/better than what existed.
JavaScript is a whole different story 😆
They just add all sort of keywords and features into the language just to feel "Oh, JavaScript can do that too" 😑