MoveNext, Nadella

At some point, Microsoft introduced compiler support for async/await. Great! Awesome! Everybody immediately jumped on its bandwagon and, as herd animals do, developers all over the world began to shout:

Async! Async!

Do everything async!

There is huge peer pressure now, to submit and subscribe to the async paradigm. Great! Awesome!

But here comes an inconvenient truth: Microsoft forgot/neglected to adjust its Reflection namespace to async paradigm. I rather suggest that they neglected but who am I to rain on their parade?

Ever did this from your method?

MethodBase.GetCurrentMethod().Name

only to see MoveNext? That is because... [long-whinded explanation of how async rewrites your method into a state machine whose last-called method is MoveNext]...

That's what Microsoft says. They prefer not to say that they forgot/neglected to make corresponding changes in Reflection, to compensate millions of .NET developers and their companies' owners/investors for their having to change their debugging code that used to work perfectly well in synchronous mode to the wonderful new asynchronous.

Microsoft are enemies of human race, and they have to be shown their place, with repercussions for being rude, obnoxious, irresponsible, monopolistic dictators.

Posted by: LinuxLies at 11:06 AM | No Comments | Add Comment
Post contains 174 words, total size 1 kb.