<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><br class=""><blockquote type="cite" class=""><div class=""><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">And other people complained about that!</span><br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""></div></blockquote></div>If I learned anything from Swift evolution, than it is that there are terrifying differences in the perception of things ;-)<div class="">— Some want to get rid of object orientation, others are fond of it</div><div class="">— Some want to enforce that "self." has always to be written out, others are asking for ways to skip it in closures</div><div class="">— Some don't want to use mailing lists, others don't want to move to a forum… ;-)</div><div class=""><br class=""></div><div class="">That's one reason why I became sceptical towards the whole evolution process:</div><div class="">Whatever direction Swift takes, it can't make everyone happy — but changing directions all the time imho is worse than a bunch of bad decisions</div></body></html>