when concurrency abstractions like fibers and queues and stms, so amazingly hide away the complexities of managing concurrent and parallel software, it signifies the amount of work that has been gone, in abstracting out patterns common to all forms of parallel and concurrent execution, and not only that, exposing it, in a well thought out, amazingly well designed, api. because both are important. not only the richness in the identification and abstraction of domain patterns, but also the clarity to expose it via an api with high usability.
when concurrency abstractions like fibers and queues and stms, so amazingly hide away the complexities of managing concurrent and parallel software, it signifies the amount of work that has been gone, in abstracting out patterns common to all forms of parallel and concurrent execution, and not only that, exposing it, in a well thought out, amazingly well designed, api. because both are important. not only the richness in the identification and abstraction of domain patterns, but also the clarity to expose it via an api with high usability.