<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><blockquote type="cite" class=""><div class="">On May 16, 2016, at 2:06 PM, Chris Lattner via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:</div><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""><blockquote type="cite" class=""><div class="">On May 16, 2016, at 11:33 AM, Tim Hawkins <<a href="mailto:tim.thawkins@gmail.com" class="">tim.thawkins@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><p dir="ltr" class="">At what point would you consider the Linux product to be viable for production server side application development. Do you think that goal has been achieved in swift 3.0. Or is it going to have to wait for the ABI lock down. </p></div></blockquote>I'm not an expert in the Linux communities needs and desires. That said, from what I understand, they don’t care at all about ABI stability, since everything is typically built from source.</div></div></div></blockquote><div><br class=""></div>I think it would be more appropriate to say that the server development community generally doesn't care deeply about ABI stability (although even there I'm sure there are exceptions). There are a lot of client-side efforts that have very different requirements from that, though.</div><div><br class=""></div><div>John.</div></body></html>