Yes, but the main question is: what for? You can't use it even to do what it's been created for: writing iOS apps (maybe some backend modules if you're obstinate enough). There is a great choice of languages in Linux with rich libraries and vibrant communities - why on Earth should I choose Swift?

I'm an iOS developer and I use it for writing iOS apps, testing, and managing my test environments. I have the luxury of assuming a macOS host though.

I think the reason you'd pick it for a server language is because the strengths of the language and ecosystem meet your server requirements.

I agree that it currently isn’t the most productive choice for most, but Swift wasn’t created just for writing iOS apps (at the least, it targeted desktops, too, from the start), and certainly aims much wider today. https://swift.org/about/:

”The goal of the Swift project is to create the best available language for uses ranging from systems programming, to mobile and desktop apps, scaling up to cloud services”

And if “doesn’t have rich libraries and vibrant communities” were a decisive argument to not start using a new language, there never would be a new language again. I can see that, for some, using Swift on the server could be the right choice (for example because it makes it easier to share code between server and iOS apps)

Some developers use Rust for Linux libraries, I use Swift for web server on Linux. The only concern I have is working with Linux libraries can be fairly difficult as you get in Rust.

Same reason a JavaScript developer uses Node.