I really hope that the concurrency bulletpoint has an “on linux, too” implicitly at the end of it, but having poked at the swift ecosystem enough to figure out if i should write a project in it, that seems unlikely.
Can you elaborate? Swift’s been putting a lot of effort into removing Apple-platform dependencies, like reimplementing the Foundation framework, so I’d assume that new features would be cross platform.
Earlier this year I scouted it for a project, while there are a handful of Linux libraries, pretty much every single library I looked at was Apple-only, including the cryptographic libraries. There are replacements for most of them but the general trend is “what’s the likelihood that this library will continue to exist in 5 years time? Slim, because it was written by one person and hasn’t been updated in a year or two”.
Concurrency support is a language-level feature rather than a library. It’s a central prerequisite for Swift’s server use case, whose expected main platform is Linux. You can watch the activities and goals of the Swift Server Workgroup to track that line of interest.
When you talk about cryptography in Swift I think of Apple’s swift-crypto, though I haven’t explored it. Its repo claims,
Swift Crypto is an open-source implementation of a substantial portion of the API of Apple CryptoKit suitable for use on Linux platforms. It enables cross-platform or server applications with the advantages of CryptoKit.
…
Swift Crypto exposes the portions of the CryptoKit API that do not rely on specialised hardware to any Swift application.
To my ears that resembles the way the swift-foundation project relocates important ingredients from Apple platform libraries to multiplatform libraries. What was your assessment?
I really hope that the concurrency bulletpoint has an “on linux, too” implicitly at the end of it, but having poked at the swift ecosystem enough to figure out if i should write a project in it, that seems unlikely.
Can you elaborate? Swift’s been putting a lot of effort into removing Apple-platform dependencies, like reimplementing the Foundation framework, so I’d assume that new features would be cross platform.
Earlier this year I scouted it for a project, while there are a handful of Linux libraries, pretty much every single library I looked at was Apple-only, including the cryptographic libraries. There are replacements for most of them but the general trend is “what’s the likelihood that this library will continue to exist in 5 years time? Slim, because it was written by one person and hasn’t been updated in a year or two”.
Concurrency support is a language-level feature rather than a library. It’s a central prerequisite for Swift’s server use case, whose expected main platform is Linux. You can watch the activities and goals of the Swift Server Workgroup to track that line of interest.
Not meaning to be snippy, but, one would think cryptographic libraries would be important to server uses cases, alas,
When you talk about cryptography in Swift I think of Apple’s swift-crypto, though I haven’t explored it. Its repo claims,
…
To my ears that resembles the way the swift-foundation project relocates important ingredients from Apple platform libraries to multiplatform libraries. What was your assessment?