<story><title>Go vs. Swift [pdf]</title><url>https://github.com/jakerockland/go-vs-swift/blob/master/go-vs-swift.pdf</url></story><parent_chain></parent_chain><comment><author>chmike</author><text>I don&amp;#x27;t see any &amp;quot;strength&amp;quot; in the classical object oriented programming model as found in C++ or Java. Actually, in modern programming composition is considered superior to inheritance.&lt;p&gt;The interface concept of Go makes programming with composition much more flexible and powerful than with the class model. The author skips this Go specific and original interface typing. This provides a multiple inheritance equivalent without all the complications on C++ and that most OO oriented languages forbid because of that complication.&lt;p&gt;Go is a very original language in this aspect as well as with concurrency. Understanding and mastering these properties goes beyond simple syntax analysis.&lt;p&gt;To me the most remarkable property of Go is its simplicity. As I explained to a friend who is a strong advocate of D, the difference with other programming language is the same as dealing with a spoken language of 1000 words instead of 10,000 words. It&amp;#x27;s true that the language with 10,000 words is more expressive and richer. But the effort required to learn, read and write a language of 1000 words is much lower than a with a language of 10000 words. I&amp;#x27;m beyond 50 years old, and too me this makes a huge difference. The best way to express it is that &lt;i&gt;with Go programming is fun again&lt;/i&gt;. I hope that Go will preserve this simplicity. At the beginning Java was simple too. They later killed it to the point I don&amp;#x27;t want to deal with Java code anymore.</text></comment>
<story><title>Go vs. Swift [pdf]</title><url>https://github.com/jakerockland/go-vs-swift/blob/master/go-vs-swift.pdf</url></story><parent_chain></parent_chain><comment><author>seanalltogether</author><text>The more I use swift, the more I&amp;#x27;ve grown to appreciate the concept of Optionals and how the compiler enforces it&amp;#x27;s usage. I have found that my swift code is more robust and explicit than my ObjC or Android java code is, as well as the team members around me.</text></comment>