Go vs. Swift [pdf]

#1

Post by jakerockland » Wed, Jan 18, 2017, 9:51 PM UTC

Go vs. Swift [pdf]
github.com

Re: Go vs. Swift [pdf]

#2

Post by zatkin » Wed, Jan 18, 2017, 10:56 PM UTC

I'm confused as to why this piece was written using LaTeX.

Re: Go vs. Swift [pdf]

#3

Post by yvsong » Wed, Jan 18, 2017, 10:57 PM UTC

Swift: better OO, syntax, IDE; Go: built-in concurrency;

Swift is a great joy for iOS development, where compatibility with Objective C makes things smooth, and operation queues are good enough for concurrency. Xcode is a big productivity booster. Good to break Swift's own backward compatibility with new releases to keep innovation, while providing a quick fix tool. Hope it will become a great server language too.

Re: Go vs. Swift [pdf]

#4

Post by tnecniv » Wed, Jan 18, 2017, 11:07 PM UTC

zatkin wrote: post #2

I'm confused as to why this piece was written using LaTeX.

Why? The LaTeX required to produce a PDF like that is no more complicated than your favorite format.

Re: Go vs. Swift [pdf]

#5

Post by robert_foss » Wed, Jan 18, 2017, 11:08 PM UTC

zatkin wrote: post #2

I'm confused as to why this piece was written using LaTeX.

It's soo pretty.

Re: Go vs. Swift [pdf]

#6

Post by seanalltogether » Wed, Jan 18, 2017, 11:10 PM UTC

The more I use swift, the more I've grown to appreciate the concept of Optionals and how the compiler enforces it'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.

Re: Go vs. Swift [pdf]

#7

Post by blario » Wed, Jan 18, 2017, 11:11 PM UTC

Very basic comparison. Doesn't go into the quality of the generated code, compiler speed or efficiency, etc.

Re: Go vs. Swift [pdf]

#8

Post by burntcookie90 » Wed, Jan 18, 2017, 11:19 PM UTC

seanalltogether wrote: post #6

The more I use swift, the more I've grown to appreciate the concept of Optionals and how the compiler enforces it'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.

make sure you check out kotlin then, for Android

Re: Go vs. Swift [pdf]

#9

Post by ajmurmann » Wed, Jan 18, 2017, 11:26 PM UTC

yvsong wrote: post #3

Swift: better OO, syntax, IDE; Go: built-in concurrency; Swift is a great joy for iOS development, where compatibility with Objective C makes things smooth, and operation queues are good enough for concurrency. Xcode is a big productivity booster. Good to break Swift's own backward compatibility with new releases to keep innovation, while providing a quick fix tool. Hope it will become a great server language too.

I never understand the praise for XCode. I love the iOS specific features like GUI creator out property explorer. But the text editor part is just awful compared to anything else I've used (primarily JetBrains IDEs, but also vim, sublime and some atom). On top of that it also has comparatively poor git integration.

Edit: one thing I forgot is the very slow feedback at least when editing Swift. For syntax error notifications to get updated sometimes takes tens of second which can be very confusing.

Re: Go vs. Swift [pdf]

#10

Post by bsaul » Wed, Jan 18, 2017, 11:37 PM UTC

yvsong wrote: post #3

Swift: better OO, syntax, IDE; Go: built-in concurrency; Swift is a great joy for iOS development, where compatibility with Objective C makes things smooth, and operation queues are good enough for concurrency. Xcode is a big productivity booster. Good to break Swift's own backward compatibility with new releases to keep innovation, while providing a quick fix tool. Hope it will become a great server language too.

Everything you saîd about swift is correct for small sized projects. The story becomes much much different once you work on a piece of code for a few months with a team. Then xcode crashes, swift builds slowly ( in minutes), you start to be crippled because of the compiler and tool.

I hate to say it, but It's not production ready yet, at least not for a big project.