The first part is semantics, yes I understand that python is running one OS thread at a time with a GIL (for now). Just pretend I used the word "concurrent" ins

The first part is semantics, yes I understand that python is running one OS thread at a time with a GIL (for now). Just pretend I used the word "concurrent" instead of parallel in all the places necessary to remove the semantic disagreement. Whether threads and joining vs async/await is clearer is a matter of taste and familiarity. I find async/await much more clear because that's what I am more used to. Others will disagree, that's fine. I suspect more people will prefer async/await as time goes on but that's my opinion. > not worrying about marking functions as async or not is a great boon to development. I don't really see why this is a big deal. You can change the function and callers can change their callsite. There are automated lint steps for this in python and javascript that I use all the time. It's not any different to me than adding an argument or changing a function name.