I would like to propose that basic crypto be part of the core libraries of swift. It seems a large oversight that this isn’t a core part of the runtime. Many if not all modern languages provide the ability to perform hashing, encryption, certificates, etc. out of the box.
I believe that any serious app developer should be encrypting their customer’s data client side; and with the Swift runtime today, I cannot write a pure Swift app without having to resort to bridging into the CommonCrypto C library. While this works, in my view, this is a hack used to bridge the gap of missing functionality. I also don’t think developers should be using libraries they find out on Github or other places. While the developers of those projects may have the best of intentions, I think it best that functionality of this sort come from the language runtime itself, that is part of the core libraries out of the box. As Swift looks to move beyond just iOS/OS X, crypto will become an ever increasingly important aspect of the core libraries such AES and RSA encryption, HMAC SHA1/256 hashing, etc. Thank you, Travis Beech | Principal Developer | Unwired Revolution Optimizing Operations for Mobile and Distributed Systems
_______________________________________________ swift-corelibs-dev mailing list swift-corelibs-dev@swift.org https://lists.swift.org/mailman/listinfo/swift-corelibs-dev
