Agreed. I&#x27;m not sure why you were downvoted. If we are speaking strictly about iOS, you are 100% right. Swift is king.<p>Swift is set to replace Objective-C and it has risen in popularity and adoption at an insanely rapid pace.<p>Everyone is adding swift to their code base. Our watch-client for example, is written exclusively in Swift. We have a ton of C++ code too. It&#x27;s not a problem because it&#x27;s all wrapped in an Objective-C API anyways.<p>Besides, Swift brings a lot more to the table than just saner syntax and less boiler plate. It also includes: a <i>good</i> type system, optionals, functional constructs, excellent OOP support, excellent error handling, scripting support, a repl, a great intermediate language in SIL, <i>cross-platform</i> (freeBSD soon) native code.<p>Sure, it&#x27;s not purely functional by any means, but it&#x27;s neither is Rust. It&#x27;s a <i>good</i> (not perfect) multi-paradigm language that can and will eat up a lot of the domain space C++&#x2F;Go&#x2F;Rust share for native applications.<p>I even predict it will go a step further. Swift will, in my prediction, eventually allow for safe, zero-overead memory management abstractions similar to Rust (and to a lesser extent C++). This will make it a head on competitor with Rust and C++ for virtually all their use cases (except legacy support).<p>My speculations is based on comments from the language&#x27;s creator expressing desire for these features in Swift [0] [1].<p>[0] <a href="https:&#x2F;&#x2F;www.reddit.com&#x2F;r&#x2F;rust&#x2F;comments&#x2F;3vadg8&#x2F;swift_is_open_source&#x2F;cxnu2kk" rel="nofollow">https:&#x2F;&#x2F;www.reddit.com&#x2F;r&#x2F;rust&#x2F;comments&#x2F;3vadg8&#x2F;swift_is_open_...</a><p>[1] <a href="https:&#x2F;&#x2F;lists.swift.org&#x2F;pipermail&#x2F;swift-evolution&#x2F;Week-of-Mon-20151214&#x2F;003494.html" rel="nofollow">https:&#x2F;&#x2F;lists.swift.org&#x2F;pipermail&#x2F;swift-evolution&#x2F;Week-of-Mo...</a>