I don't think this is fair to Swift. Swift seems to have taken a view that the langauge will force you to be explicit about what you want. For example, the "indirect" keyword. Early Swift did not let you have recursive enums, apparently this can be something of a performance killer I guess was the reasoning. However they are really useful, so Swift added them. However rather than just automatically using an indirect Enum which is easily detectible, Swift forces you to use the "indirect" keyword. Rather than implicitly doing work for you, the Swift compiler stops to ask "are you sure this is what you really want to do? Do you understand the tradeoffs you are making?"<p>Personally I'm a fan of the Swift approach even if it does balloon the keyword count a bit.
Depending on how you count keywords, SQL has over 400. See <a href="https://github.com/ballista-compute/sqlparser-rs/blob/main/src/dialect/keywords.rs" rel="nofollow">https://github.com/ballista-compute/sqlparser-rs/blob/main/s...</a> .<p>SQLite has 147 keywords - <a href="https://www.sqlite.org/lang_keywords.html" rel="nofollow">https://www.sqlite.org/lang_keywords.html</a> .
VB6 has close to 300<p>And while some vb6 code is truly terrible, it isn't because of keywords. It's because beginners have no idea what they are doing.<p>So I imagine Swift code may be terrible because there are a lot of noobs out there doing whatever it takes to ship.
56 keywords in OCaml, 99 total if you count the character sequences. Maybe a better metric would be "keywords uses regularly"?. <a href="https://ocaml.org/manual/lex.html#sss:keywords" rel="nofollow">https://ocaml.org/manual/lex.html#sss:keywords</a>
Smalltalk80 wins with only 6 keywords <a href="https://en.wikipedia.org/wiki/Smalltalk" rel="nofollow">https://en.wikipedia.org/wiki/Smalltalk</a>