Creating many “clients” vs wrapping a “client” in an actor

[lukasa (Cory Benfield)]

@taylorswift

after all, why must accessing a ClientBootstrap require synchronization in the first place?

Because they aren't Sendable. They're a giant pile of mutable state without synchronzation: you really, genuinely cannot use them in multiple concurrency domains. These not being Sendable is not an oversight, it's an intentional design decision.

@sliemeobn

I also believe that creating a bootstrap is not exactly a "heavy" operation, so it's probably rarely worth adding a ton of threadsafety complexity around it.

This is accurate: ClientBootstraps are cheap, feel free to create plenty.

We've got tentative plans to deprecate-and-replace the current bootstraps, because they aren't really serving their purpose well anymore. In particular the builder pattern has aged poorly. The next versions will likely be value types, which makes this entire problem go away.