I think the thing is though, at least in JS it's easier to transition. In .NET if you use go async, it has to be async all the way (or use some god aweful method of running async, synchronously). So that touches every method, and given the "best practice" of adding a

Async

suffix means re-implementing every method.

Yeah, it's a pain, and it only gets more painful as time goes on - I'm not dismissing that. But, I often hear async still talked about as if it's some obscure new-fangled nice-to-have, as opposed to the standard for building web apps for the last decade. I'd love to change the narrative on this in the Umbraco community.

I hear ya. I think if I was building something greenfield it would defo be async all the way. I defo should have looked at it closer when building Vendr for the first time. Unfortunately it was "yet another thing I didn't know about" and so was lower priority, but indeed that comes at a cost the larger the project grows.

I think a good place to start would be apis used when creating frontends. Routing has had some improvements somewhat recently in this respect. I did have a go at making the repositories async if anyone is keen on picking up where I left off. https://github.com/umbraco/Umbraco-CMS/pull/12537