<story><title>Swift 6</title><url>https://www.swift.org/blog/announcing-swift-6/</url></story><parent_chain><item><author>jakey_bakey</author><text>Swift would be perfect if it wasn&amp;#x27;t dying a death by 1000 cuts thanks to the inherent conflict in its governance.&lt;p&gt;Swift is caught between two clans: the Swift Working Group™ open-source community, and the Apple corporate entity who pays most of their salaries. Both have their own incentives and their own imperfections, but you guess who has the majority influence.&lt;p&gt;Ridiculous, permanent, tech debt such as hardcoded compiler exceptions are permanently living in the compiler codebase. Even worse, half-baked concepts such as result builders are pushed through without any real discussion because Apple wants the SwiftUI syntax to look pretty.&lt;p&gt;It&amp;#x27;s an amazing language still, but I can&amp;#x27;t see it surviving as nicely in the next 10 years if Apple doesn&amp;#x27;t learn to let go.</text></item></parent_chain><comment><author>paperplatter</author><text>If I were new to Swift and saw how complicated and version-specific the Stackoverflow answers* are for things that are super simple in other languages, I wouldn&amp;#x27;t expect things to get much easier from there. And that instinct would be right.&lt;p&gt;* &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;stackoverflow.com&amp;#x2F;questions&amp;#x2F;34540185&amp;#x2F;how-to-convert-index-to-type-int-in-swift&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;stackoverflow.com&amp;#x2F;questions&amp;#x2F;34540185&amp;#x2F;how-to-convert-...&lt;/a&gt; &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;stackoverflow.com&amp;#x2F;questions&amp;#x2F;32305891&amp;#x2F;index-of-a-substring-in-a-string-with-swift&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;stackoverflow.com&amp;#x2F;questions&amp;#x2F;32305891&amp;#x2F;index-of-a-subs...&lt;/a&gt;  &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;stackoverflow.com&amp;#x2F;questions&amp;#x2F;39677330&amp;#x2F;how-does-string-substring-work-in-swift&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;stackoverflow.com&amp;#x2F;questions&amp;#x2F;39677330&amp;#x2F;how-does-string...&lt;/a&gt; &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;stackoverflow.com&amp;#x2F;questions&amp;#x2F;24250938&amp;#x2F;swift-pass-array-by-reference&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;stackoverflow.com&amp;#x2F;questions&amp;#x2F;24250938&amp;#x2F;swift-pass-arra...&lt;/a&gt;</text></comment>
<story><title>Swift 6</title><url>https://www.swift.org/blog/announcing-swift-6/</url></story><parent_chain><item><author>jakey_bakey</author><text>Swift would be perfect if it wasn&amp;#x27;t dying a death by 1000 cuts thanks to the inherent conflict in its governance.&lt;p&gt;Swift is caught between two clans: the Swift Working Group™ open-source community, and the Apple corporate entity who pays most of their salaries. Both have their own incentives and their own imperfections, but you guess who has the majority influence.&lt;p&gt;Ridiculous, permanent, tech debt such as hardcoded compiler exceptions are permanently living in the compiler codebase. Even worse, half-baked concepts such as result builders are pushed through without any real discussion because Apple wants the SwiftUI syntax to look pretty.&lt;p&gt;It&amp;#x27;s an amazing language still, but I can&amp;#x27;t see it surviving as nicely in the next 10 years if Apple doesn&amp;#x27;t learn to let go.</text></item></parent_chain><comment><author>Vegenoid</author><text>&amp;gt; Ridiculous, permanent, tech debt such as hardcoded compiler exceptions are permanently living in the compiler codebase.&lt;p&gt;A little search-engining didn’t surface info about this, could you point me in the right direction?</text></comment>