Very feasible. From embedded (https://www.swift.org/blog/embedded-swift-examples/) to Linux apps (https://www.swift.org/blog/adwaita-swift/) to tiny games (https://www.swift.org/blog/byte-sized-swift-tiny-games-playd...) to ML (https://www.swift.org/blog/mlx-swift/) to Windows (https://www.swift.org/blog/swift-everywhere-windows-interop/) to Private Cloud Compute (https://github.com/apple/security-pcc)...

I’ve been using it for a hobby project targeting a Linux server deployment. It’s good, and I don’t think the Apple ties are what’s holding it back now, I think it’s a relative lack of good frameworks and libraries. What’s there is often excellent quality, but it’s still a bit hit and miss even for common library use cases.

I often think about what my day-1 stack would be for a new company. Swift would be on the table as an option.

Indeed, it’s technically possible, but the level of discomfort, workarounds and paper cuts to get there makes it entirely a hobby thing.

If you really want to make “something” for the purpose of using Swift go ahead. If you want to make something, there are plenty of attentives to choose from.

If you stick with x86_64 land and > Swift 6.0, there is nothing infeasible about it.