<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;" class=""><div dir="auto" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi Travis,<div class=""><br class=""></div><div class="">I think the best path for projects to become part of the corelibs “umbrella” is to start them off as community-driven, and once they have gained enough momentum we should consider folding them into the core distribution.</div><div class=""><br class=""></div><div class="">This provides a lot of key benefits. Most importantly, the new project will have clear ownership and responsibility. We need to make sure that the right people are there to represent its interests to the larger Swift effort. Also, we’ll know who to talk to to deal with general issues like keeping it up to date with language changes, integrating it with CI, considering API changes, etc.</div><div class=""><br class=""></div><div class="">- Tony</div><div class=""><br class=""></div><div class=""><div><blockquote type="cite" class=""><div class="">On Apr 14, 2016, at 3:53 PM, Travis Beech via swift-corelibs-dev <<a href="mailto:swift-corelibs-dev@swift.org" class="">swift-corelibs-dev@swift.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" class="">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; font-size: 14px; font-family: Calibri, sans-serif;" class="">
<div class="">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 class=""><br class="">
</div>
<div class="">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 class=""><br class="">
</div>
<div class="">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 class=""><br class="">
</div>
<div class="">Thank you,</div>
<div class="">
<div id="" class="">
<div class="">
<div class=""><br class="">
</div>
</div>
<div class="">
<div class="">Travis Beech<span style="font-family: Calibri; font-size: 12px;" class=""> | </span><span style="font-size: 12px;" class="">Principal Developer</span><span style="font-family: Calibri; font-size: 12px;" class=""> | </span><span style="font-size: 12px;" class="">Unwired Revolution</span></div>
<div class=""><b style="font-family: Calibri; font-size: 12px;" class=""><font color="#0064a1" class="">Optimizing Operations for Mobile and Distributed Systems</font></b></div>
</div>
</div>
</div>
</div>
_______________________________________________<br class="">swift-corelibs-dev mailing list<br class=""><a href="mailto:swift-corelibs-dev@swift.org" class="">swift-corelibs-dev@swift.org</a><br class="">https://lists.swift.org/mailman/listinfo/swift-corelibs-dev<br class=""></div></blockquote></div><br class=""></div></div></body></html>