by blacktriangle on 7/30/21, 6:17 PM
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.
by eesmith on 7/30/21, 7:10 PM
by vb6sp6 on 7/30/21, 5:35 PM
VB6 has close to 300
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.
by hpen on 7/30/21, 6:53 PM
And yet code in Swift is much cleaner than anything in Javascript. I say that having mostly written Swift & Javascript at my jobs and on the side.
by wdb on 7/30/21, 6:55 PM
Yeah, the design by committee approach of Swift isn't helping either. There are some weird language decisions being made
by Zababa on 7/31/21, 12:55 AM
by xq3000 on 7/31/21, 7:02 AM
by mmphosis on 7/30/21, 6:31 PM
by cweill on 7/31/21, 4:33 AM
I don't see golang on that chart. It must be close to C (on the lower end).
by ksaj on 7/30/21, 8:35 PM
I'm pretty sure Common Lisp has well over 100 keywords.
by BooneJS on 7/30/21, 8:27 PM
SystemVerilog (IEEE 1800-2017) has 248.