Swift's complexity has grown, true, but's it's also grown alongside the number and nature of the problems it's being asked to solve.

When first introduced I remember people complaining about optionals and how Apple was forcing them to handle them... even though mishandling them resulted in about 30% of the runtime crashes at the time.

Protocols gave rise to existential types, SwiftUI, to opaque types. But in both cases most of the complexity is hidden most of the time.

Structured concurrency is the hot button today, but basically we're asking the compiler to find and solve a higher order of problems for us, before they become problems for our users.

I also think you're over maligning Apple, as well as the folks over at Swift Evolution, but that's another tale.

I've used quite a few languages over the years, but Swift, I think, is my favorite. Yes it still has a few rough spots, but on the other hand...

It's only ten years old.