> Unified event handling: All object types have a signaled state, whose semantics are specific to each object type. For example, a process object enters the sig

> Unified event handling: All object types have a signaled state, whose semantics are specific to each object type. For example, a process object enters the signaled state when the process exits, and a file handle object enters the signaled state when an I/O request completes. This makes it trivial to write event-driven code (ehem, async code) in userspace, as a single wait-style system call can await for a group of objects to change their state—no matter what type they are. Try to wait for I/O and process completion on a Unix system at once; it’s painful. Hahaha. Try polling stdin, a pipe, an ipv4 socket, and an ipv6 socket at the same time.