<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="">Your patience in the face of my hysterics is truly inspirational (no sarcasm!). <div class=""><br class=""></div><div class="">I just want to say up front that I hope none of my emails come across as an attack. They are just coming from a place of passion. Based on your rational responses to me, I think you do understand that :)</div><div class=""><br class=""></div><div class="">I am <b class="">not </b>concerned about Swift not letting me do something. I am concerned about the fun and beauty of the resulting code.</div><div class=""><br class=""></div><div class="">For example, I got into Objective-C because it was fun. It can read like poetry with its verbose methods and was so much simpler to me than other languages like C/C++/Java.</div><div class=""><br class=""></div><div class="">My fear is that this fun will be removed from Swift after I have invested so much time into it. </div><div class=""><br class=""></div><div class="">I can still be productive because Swift still allows me to build things.</div><div class=""><br class=""></div><div class=""><b class="">But will it be as fun </b>in the future? Will it just feel like C++…all sterile and very bleep bloop bloopy (my description of what people PICTURE in their heads when they think of people programming…you know their impression that we are just typing 0s and 1s).</div><div class=""><br class=""></div><div class="">I had the luxury of coming into Objective-C near the end, so I didn’t have to go through all the syntax changes (well some of them). Maybe if I had joined ObjC from the beginning I would have either hated or loved the direction it was going. It’s hard to say.</div><div class=""><br class=""></div><div class="">Coming into a brand new language is much different to say the least. Swift 1 and 2 introduced a very beautiful and expressive language in my opinion. Swift 3 is still expressive, but with some of these proposals, it feels like some of that is being stripped away little by little and it is a very uncomfortable feeling</div><div class=""><br class=""></div><div class="">My concerns may be unfounded. I just fear that the simplicity that brought me to Objective-C and then Swift will be lost over time if it starts turning into something as complex as C++ (which I do not enjoy writing in).</div><div class=""><br class=""></div><div class="">I hope this makes some sense about my perspective</div><div class="">Brandon</div><div class=""><br class=""></div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Jun 10, 2016, at 3:52 PM, Xiaodi Wu <<a href="mailto:xiaodi.wu@gmail.com" class="">xiaodi.wu@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" style="font-family: Helvetica; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><div class="gmail_extra"><div class="gmail_quote">On Fri, Jun 10, 2016 at 2:38 PM, Brandon Knope via swift-evolution<span class="Apple-converted-space"> </span><span dir="ltr" class=""><<a href="mailto:swift-evolution@swift.org" target="_blank" class="">swift-evolution@swift.org</a>></span><span class="Apple-converted-space"> </span>wrote:<br class=""><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex;">Thanks for the laugh!<br class=""><br class="">The last week or so is actually stressing me out about the direction where swift is going…<br class=""><br class="">I hope it is just a fleeting feeling but that remains to be seen. I am beginning to think my interests and taste are no longer aligning with the communities or core teams.<br class=""><br class="">Brandon<br class=""></blockquote><div class=""><br class=""></div><div class="">I think, given the usage statistics, we'll find that these amount to small nips and tucks. I can't speak to whether things will be to your taste, but please rest assured that these proposals do not arise out of anyone's taste or distaste (outside that of the core team). If taste were the basis for proposals, I'd be proposing rather larger changes to the syntax, but I appreciate that my personal taste is of no import.</div><div class=""><br class=""></div><div class="">But as to interests, please do speak loudly and without reserve if any proposed changes are putting a stop to real-world (or even anticipated) uses you have. That's precisely what this process is about.<br class=""></div><div class=""> </div><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex;"><div class="HOEnZb"><div class="h5"><br class="">> On Jun 10, 2016, at 3:25 PM, L. Mihalkovic via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:<br class="">><br class="">> Goodness... where is this language going.....<br class="">><br class="">>> On Jun 10, 2016, at 9:08 PM, Erica Sadun via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:<br class="">>><br class="">>><br class="">>>> On Jun 10, 2016, at 1:06 PM, Rob Norback via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:<br class="">>>><br class="">>>> Following Brent's logic that the for-in where should mimic the switch statement functionality, then this example:<br class="">>>><br class="">>>> for (eachKey, eachValue)<br class="">>>> where eachValue > 5<br class="">>>> in theKeyValuePairs {... }<br class="">>><br class="">>> <squish><br class="">>><br class="">>> I finally convinced myself of which direction I wanted to go:<span class="Apple-converted-space"> </span><a href="https://github.com/apple/swift-evolution/pull/362/files" rel="noreferrer" target="_blank" class="">https://github.com/apple/swift-evolution/pull/362/files</a><br class="">>><br class="">>> Related blog post here:<span class="Apple-converted-space"> </span><a href="http://ericasadun.com/2016/06/10/swift-where-oh-where-can-my-where-clause-be/" rel="noreferrer" target="_blank" class="">http://ericasadun.com/2016/06/10/swift-where-oh-where-can-my-where-clause-be/</a><br class="">>><br class="">>> Big thanks to Brent and Wux.<br class="">>><br class="">>> -- E<br class="">>><br class="">>><br class="">>><br class="">>><br class="">>> _______________________________________________<br class="">>> swift-evolution mailing list<br class="">>><span class="Apple-converted-space"> </span><a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a><br class="">>><span class="Apple-converted-space"> </span><a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank" class="">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br class="">> _______________________________________________<br class="">> swift-evolution mailing list<br class="">><span class="Apple-converted-space"> </span><a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a><br class="">><span class="Apple-converted-space"> </span><a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank" class="">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br class=""><br class="">_______________________________________________<br class="">swift-evolution mailing list<br class=""><a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a><br class=""><a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank" class="">https://lists.swift.org/mailman/listinfo/swift-evolution</a></div></div></blockquote></div></div></div></div></blockquote></div><br class=""></div></body></html>