The loudest and most glaring condemnation of async is Visual Studio

Async breaks up methods into several, and no amount of < tt>ConfigureAwait(false) can fix that. It's N times more stack allocation/deallocation, N times more overhead, N times more complexity. As a result, all code that awaits async is N times slower than synchronous code. That's the sacrifice the humankind pays for subscribing to Microsoft's dogma.

Visual Studio has become slow as fuck. From 2005-2008 that were FAST we arrived at mediocre 2015, bad 2017, horrible 2019 and disastrous 2022 that can't find its ass with both hands. Along the way, they gradually became more and more asynchronous, porous, gooey, and slimy. I am somewhat even baffled by its slowness because, having been developing in async WPF MVVM under orders from my superiors, I am still able to deliver reasonably fast desktop GUI products. The slowness of Visual Studio 2022 is mind-boggling! It's abysmal. They do something so horridly wrong that it takes considerable time to do any operation, and this is on a very fast machine that runs any other software impressively fast.

When the owner of the OS, framework, development tool, and the final product so utterly fails to deliver performance, it should serve as a wakeup call: something is fundamentally wrong with them.

Posted by: LinuxLies at 08:33 AM | No Comments | Add Comment
Post contains 226 words, total size 1 kb.