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?"
Personally I'm a fan of the Swift approach even if it does balloon the keyword count a bit.
I feel it's better to add keywords like that than to over load keywords based on context. See the keyword const in C/C++.
Also better to trust the end used to decide what trade offs they want to make. For instance code that converts a user click to a database query, clean and understandable is more important than performance. If it takes 10ns or 10ms the user ain't going to know the difference.
Can you give some examples? IIUC there are builtins (macros/functions that couldn't be expressed in the language) but no keywords. There are lots of syntax elements that could be keywords like ' (quoting) but I am not aware of any true keywords.
blacktriangle|4 years ago
Personally I'm a fan of the Swift approach even if it does balloon the keyword count a bit.
Gibbon1|4 years ago
Also better to trust the end used to decide what trade offs they want to make. For instance code that converts a user click to a database query, clean and understandable is more important than performance. If it takes 10ns or 10ms the user ain't going to know the difference.
eesmith|4 years ago
SQLite has 147 keywords - https://www.sqlite.org/lang_keywords.html .
nn3|4 years ago
vb6sp6|4 years ago
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.
So I imagine Swift code may be terrible because there are a lot of noobs out there doing whatever it takes to ship.
hpen|4 years ago
philwelch|4 years ago
wdb|4 years ago
Zababa|4 years ago
xq3000|4 years ago
mmphosis|4 years ago
cweill|4 years ago
ksaj|4 years ago
kevincox|4 years ago
BooneJS|4 years ago