If it's just an API term then why don't they just call it a "user thread"? Because that might be confused with other user thread implementations? It is also si

If it's just an API term then why don't they just call it a "user thread"? Because that might be confused with other user thread implementations? It is also significantly more awkward than "fiber". Microsoft calls their implementation of a LDAP server "Active Directory" even though they are essentially the same thing. Not really; AD does a lot more than just LDAP (e.g. Kerberos, DNS).