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
Kate Gregory gave one of my favorite talks about this that has influenced how I like to think about the tradeoffs between explicit and implicit syntax: https://youtu.be/-Hb-9TUyjoo?si=tToVr-ZKBolLLh3P
@chandlerc @inthehands @airspeedswift Nice! Looking forward to watching this, thanks for sharing, Chandler
@chandlerc @airspeedswift Looks promising at a glance! In the beginning, some of the same thoughts as here:
https://hachyderm.io/@inthehands/113679908310539599
…and I like where the speaker is going about the importance of empty space. Thanks for sharing.