Chris Lattner left Swift core team
&gt; It is obvious that Swift has outgrown my influence, and some of the design premises I care about (e.g. &quot;simple things that compose&quot;)<p>As someone who was heavily invested in Swift, and an active member of the community from around 2015-2019, I&#x27;m a bit sad to see the direction the language is taking.<p>From the time I started experimenting with Swift, I absolutely loved the philosophy of the language.  It seemed to really prioritize having a set of well-factored systems, each with their own very rationally designed interfaces, which could be composed to do really powerful things.  It was an incredibly expressive language which allowed for writing code with an incredible level of clarity - when writing Swift code I always felt I was writing at the level of the problem domain, not writing syntax.  At the same time it offered really nice features for ensuring safety and correctness, like ADT&#x27;s and best-in-class nullability syntax.<p>It was a language which sometimes seemed to move at a glacial pace, but the implicit tradeoff was that when a feature landed, it was for the most part very well thought out, and would add to the language with minimal negative impact.<p>A few years ago that seemed to start to change.  From my perspective, some of the features added to the language to support SwiftUI - specifically property wrappers and function builders - very much felt rushed and forced into the language based on external deadlines.  And imo they have a largely negative impact on the language: it used to be the case that you could look at a piece of Swift code and roughly understand how it would compile to assembly pretty easily, but with these new features there&#x27;s a ton of compiler magic going on behind the scenes.