<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>AsyncAwait</author><text>I think the author misses the fact that Swift wasn&amp;#x27;t truly &amp;#x27;done&amp;#x27; when it was introduced, (and still isn&amp;#x27;t). Objective-C had some 30+ years to evolve, but Swift can&amp;#x27;t have 3?&lt;p&gt;I get that if you&amp;#x27;re shipping Swift in production you want to refactor as little as possible, but it is pretty hard to come up with the ideal design straight out of the gate. Swift can stop evolving, but it will be THEN when it loses the reason to exist. If Swift is just going to be ObjC with a nicer syntax, (or the features that YOU personally find desirable), then why bother with it at all? Swift is trying to get its design right and that takes time, at the same time I wouldn&amp;#x27;t want to be stuck with a poorly designed language for the next 30 years, so it&amp;#x27;s worth the current turbulence for me.&lt;p&gt;(Rust was the same way 2011-2015 to a MUCH bigger degree and it did in fact eventually stabilize as promised.)&lt;p&gt;If it&amp;#x27;s that much of a problem, ObjC isn&amp;#x27;t going anywhere, it&amp;#x27;s your choice.&lt;p&gt;EDIT: Fixed a typo.</text><parent_chain></parent_chain></comment><story><title>Swift&apos;s Evolution</title><url>https://carpeaqua.com/2017/06/02/swifts-evolution/</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>bsaul</author><text>I&amp;#x27;m actually pretty happy swift moves the server side story forward, because i&amp;#x27;m convinced the &amp;quot;next big language&amp;quot; will have to run on mobile and server. Actually, i think they don&amp;#x27;t go fast enough, especially regarding concurrency ( which on the server goes beyond just providing async await, as lattner said they were aiming at something closer to the actor model).&lt;p&gt;I don&amp;#x27;t think the &amp;quot;maybe objc is still relevant for new project&amp;quot; trend we&amp;#x27;ve been seeing the last few months on HN is going anywhere. I&amp;#x27;m currently in the process of converting a large codebase from objc to swift, and there is absolutely no doubt that the language is WAY better, and brings a lot of safety enhancements as well.&lt;p&gt;The only big remaining pain point now is clearly in the tooling, but now that they&amp;#x27;re stabilized the language a bit more, it&amp;#x27;s probably going to get better fast.</text><parent_chain></parent_chain></comment><story><title>Swift&apos;s Evolution</title><url>https://carpeaqua.com/2017/06/02/swifts-evolution/</url></story>