It sure seems like people have shifted their opinion on that, perhaps even subconsciously feeling now that they need to more forcefully defend positions they previously felt scared to express.

While framing certainly matters, defining a debate as resolved doesn't look like a path to success to me.

What I really wish is for .net to make blocking on async safe and reasonable, even if it's not optimal. The current approach is just a landmine, especially since it's not visible from any given api when there's blocking internally, and furthermore the cost of blocking on async is usually low.

Frankly, all of these results are great. The marginal cost of creating and awaiting a no-op promise are clearly very unlikely to ever be an issue in any real-world workload. Take the hungriest program here - Go's - that's still less than 3kb per goroutine.