This is cool but I think it&#x27;s misleading to say that Swift is a good option for starting a web backend project _today_, at least for anything that&#x27;s not hobby work. The folks at Apple update the dev builds so frequently that in my experience it breaks things often enough that you&#x27;ll spend 50% of your time updating your code for a new build or waiting for dependencies to update their code.<p>And just to be clear I think that&#x27;s awesome. I love the work they&#x27;re doing; it&#x27;s just time consuming. I&#x27;ve been writing my own approach to a Swift MVC framework so this is something I&#x27;m experiencing firsthand:<p>Swerver: <a href="https:&#x2F;&#x2F;github.com&#x2F;jparishy&#x2F;swerver" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;jparishy&#x2F;swerver</a> (example usage: <a href="https:&#x2F;&#x2F;github.com&#x2F;jparishy&#x2F;swerverorg" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;jparishy&#x2F;swerverorg</a> - it&#x27;s based on libuv and makes many choices for you a la Rails compared to the framework demoed in the OP)<p>and it has been way more time consuming that I would have expected going into it. And right now it doesn&#x27;t build on Linux because the latest Apple build broke something in CryptoSwift, which Swerver depends on.<p>All that said, Swerver has been super fun to work on so. After a lot of the hard work had been done, the actual usage (as demoed in jparishy&#x2F;swerverorg with user authentication, client-side session state, and the basic MVC&#x2F;DB access stuff) has been really smooth and enjoyable. &#x2F;shamelessplug