Anyone have any idea why the `actor` approach was removed from the documentation here? <https://kot...

# coroutines

[zak.taccardi]

Anyone have any idea why the actor approach was removed from the documentation here?

https://kotlinlang.org/docs/shared-mutable-state-and-concurrency.html

[Jeff Lockhart]

https://github.com/Kotlin/kotlinx.coroutines/issues/3785

[Casey Brooks]

The actor { } API was only ever available in JVM targets, and it was little more than a Channel. It simply was never developed beyond that, and while there has long been the desire for a new Actor API, it just hasn’t been a priority.

that’s not to say Actors or similar patterns like MVI aren’t extremely useful. It’s just that the kotlin team has effectively delegated such higher-level concurrency patterns to community libraries (like my own Ballast MVI library) so they can focus more on the lower-level stuff like you’d find in that doc, which form the basis for higher-level patterns.