<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div>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. </div>
<div><br>
</div>
<div>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.</div>
<div><br>
</div>
<div>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.</div>
<div><br>
</div>
<div>Thank you,</div>
<div>
<div id="">
<div>
<div><br>
</div>
</div>
<div>
<div>Travis Beech<span style="font-family: Calibri; font-size: medium;"> | </span><span style="font-size: 12px;">Principal Developer</span><span style="font-family: Calibri; font-size: medium;"> | </span><span style="font-size: 12px;">Unwired Revolution</span></div>
<div><b style="font-family: Calibri; font-size: medium;"><font color="#0064a1">Optimizing Operations for Mobile and Distributed Systems</font></b></div>
</div>
</div>
</div>
</body>
</html>