I read about the distributed actors and my first thought was "a semi standalone headset that needs to communicate with the phone and/or watch" could probably benefit from this.
Swift's use case for backend are those iDevice apps that also need to talk to something, so even if that is the only use case Apple cares about Swift on Linux, it is already a bigger number than many languages can aspire to.
> With distributed actors, we acknowledge that the world we live in is increasingly built around distributed systems, and that we should provide developers with better tools to work within those environments. We aim to simplify and push the state-of-the-art for distributed systems programming in Swift as we did with concurrent programming with local actors and Swift’s structured concurrency approach embedded in the language.
But this seems like a "it's a good thing to have" rather than "we need this to do that". This is not to question the choice to add those to Swift, I'm just curious about the use cases. I've done a bit of Swift and I like the language a lot. If this means that we'll see more Swift on the backend, I'm excited for it.