That's the thing though: it affects you even if you don't use it. E.g. Swift's type system was made more complex because SwiftUI needed opaque types, function builders etc. and that was shipped with little consideration or design.

> I am less concerned about the number of total keywords vs. the average number of keywords required to accomplish what I need

Onve again, they affect you even if you don't use them. Because the compiler and the libs and the systems etc. now have to aware of these, and use them extensively.

E.g.

--- start quote ---

The Compiler's semantic analysis simply looks for the raw source string "DispatchQueue.main", and adds the hidden @_unsafeMainActor attribute

https://x.com/jacobtechtavern/status/1986705344748220529

--- end quote ---

It's not language design. It's a minefield of unspecified hacks and workarounds. And the list is growing.

Speaking of SwiftUI, and how it affects the compiler https://x.com/krzyzanowskim/status/1818881302394814717

> In fact, I think C# might honestly be worse.

C# is 25 years old, Swift is 11, and already basically on par with C#? ;)

Also, "this language could he worse" is not a good argument :)

BTW that chart is outdated. It shows C# 8 (it's 14 now) and Swift 5. Swift now has twice as many keywords as C# 8 :) And as many as the Visual Basic 2019 (at 207 keywords).

> I think you can do something like this as Swift 5 or 6

Yeah, I vaguely remember something like that :)