And `go foo()` isn't hiding complex mechanisms behind language syntax?

Task { ... } isn't syntactic sugar. It's a specific instruction to the system to create an asynchronous context denoted by the task closure.

Does the developer need to be aware of it? Yep. Should the developer be aware of it? Yep.

Further, the same mechanisms are also the basis for actor interactions and Swift concurrency.

Not convinced.