Recent searches
Search options
I’ve always scoffed at the “explicit is better than implicit” maxim in programming. It’s hot nonsense.
All code has •something• that’s implicit. (Do you write out the Peano axioms every time you declare an integer?!) Deciding •what• should be implicit and what should be surfaced as explicit is one of the most difficult and important fundamental questions in language and API design. “Nothing” and “everything” are both nonsense answers.
Thought comes to me be because of this from @airspeedswift:
https://mastodon.social/@airspeedswift/113810755456672499
MastodonBen Cohen (@airspeedswift@mastodon.social)Attached: 1 image
Now I'm fully aware that there are plenty of people who still believe this code is better than Swift. But at this point I think they're a tiny minority.
This screenshot demonstrates to me the fundamental core of why Swift strives to be a low-ceremony language. Not because all the ceremony shown here is a hassle remember or type, though it is.
It's that the ceremony drowns out the core of what the code is trying to express: the business logic that is the actually important part.