Introducing Swift Service Lifecycle
Swift as a language&#x2F;ecosystem does seem to check all the boxes in contrast to other modern, mainstream languages; it looks, to me at least, like a much more ergonomic alternative for building applications compared to Rust and Go. It&#x27;s considerably faster and more type-safe than Python and Ruby. And it has a drama- and shenanigans-free licensing model that I personally am much more comfortable with as opposed to the shitshow that is Java (and, to a lesser extent, .Net).<p>I&#x27;ve been reading lots of Swift docs&#x2F;articles, and made quite a few book purchases from raywenderlich.com and hackingwithswift.com. My &quot;gut feeling&quot; tells me making the investments to become proficient in Swift, and eventually mastering it, will pay off big time.<p>As a web-focused developer, I must admit I found Objective-C and UIKit intimidating, but with SwiftUI, Apple seems to be lowering barriers to entry; if you know something like Ember, Vue, React, or Angular, you won&#x27;t struggle too much trying to grok SwiftUI.<p>With Vapor becoming a mature framework, and Apple giving its official blessing for the development of server-side Swift libraries and tools, it does seem like we may soon reach critical mass on the server, and there is a lot of appeal in being able to consolidate and develop with one language across the stack.<p>If we can get a Swift-to-Kotlin compiler and a Swift-to-JS compiler (there are already Swift-to-HTML DSLs, and I have been experimenting with a Swift-to-CSS DSL - with my limited proficiency in the language - and it does not seem totally impractical), it&#x27;s not unreasonable to imagine Swift becoming a &quot;rule them all&quot; language (I remember reading somewhere that Chris Lattner said his goal with Swift was &quot;Total World Domination&quot; and didn&#x27;t think it was that far off, but can&#x27;t find the source now).