I think there is something to be said for keeping a language simple, though. The basic semantics of a language should be comprehensible to everyone, let the standard library have all the wacky stuff someone wanted decades ago. (macros - the lisp kind, not the C kind - make this easier)

Async has been stable for a long time. Coroutines are just syntax sugar AFAIK.

What do you mean by “abstract away”, and what about it is exclusive to headers?

Eg most languages have something like a trait or interface wherein you can put a list of definitions (optionally with a default aka “inline” implementation) which are then actually implemented elsewhere. This is considered useful by everyone because it allows multiple implementations to be associated with 1 name. They are generally not desired in cases where only 1 implementation will ever be written.

AFAIK the only use case where headers accomplish the same is if they’re treated as documentation for an API that could be implemented by any library.

Admittedly certain programming styles benefit immensely from headers, despite the drawbacks to “design as you go” programming.

I would (probably not literally) wager that by “this” they meant *looks around at entire world*…

this

It tells you how to exit if you press ctrl+C, which is many people’s first instinct.

Fun fact: there’s a group that shares this goal but was actually capable of doing it: https://www.scratch.mit.edu/

(TL;DR you can just let people explore coding in a simple language/engine and that’s enough of a stepping stone)