3 ms·
You might be surprised. Check out Vapor [1] and Soto [2], which are built on Apple's SwiftNIO (non-blocking I/O) [3]. It's actually a very nice ecosystem. All t
by programmarchy 4y ago
You might be surprised. Check out Vapor [1] and Soto [2], which are built on Apple's SwiftNIO (non-blocking I/O) [3]. It's actually a very nice ecosystem. All the tools are in place to build web servers, Lambdas, etc.
[1] https://vapor.codes https://vapor.codes
[2] https://github.com/soto-project/soto https://github.com/soto-project/soto
[3] https://github.com/apple/swift-nio https://github.com/apple/swift-nio
- frou_dh 4y agoI think the point they are trying to make is that unless someone already has history as Mac/iOS app developer, they are in practice not even considering Swift when doing a project that targets Linux, regardless of how good the libraries are or are not. If we exclude the aforementioned group, then adoption of Swift for non-Apple platforms seems like an almighty bust (close to nonexistent?) compared to the lofty goals the Swift team were mentioning in the early days.
- programmarchy 4y agoFor server and system code, Swift is mostly competing with Rust and Go, as people consider fast, compiled, type safe languages. If you look at Docker downloads, Swift has 10M, Rust has 50M, and Go has 1B+. Compared to Go, yeah, it's nowhere close. But compared to Rust, I wouldn't quite call it a bust, and could see teams choosing it for the easier learning curve. So yeah, it's a relatively small niche at this point, but I also think it's fair to say the effort to make Swift a contender on the server has been more than just iOS developers being forced to make web apps.
- ragnese 4y agoI agree. I've assumed that once Lattner left as Swift lead, that Apple basically decided that Swift would be Apple-only. That's the only reasonable explanation for them adding Combine, result builders, etc into the language.