Progressive disclosure principle
Table of contents
Abstract
This proposal codifies our preference for designs that support “progressive disclosure”, meaning that programmers can ignore a given language concept (or even be unaware of it) until it is directly relevant to the task they’re doing.
Problem
Carbon’s design choices have been motivated in part by a desire for “progressive disclosure”, but that approach has not been codified as a design principle.
Proposal
See (docs/project/principles/progressive_disclosure.md)[/docs/project/principles/progressive_disclosure.md], which is introduced by this proposal.
Rationale
In order to have a vibrant community and culture, Carbon needs to be effectively teachable and learnable. Progressive disclosure supports that goal by minimizing the amount that must be learned at any one time, and by enabling concepts to be introduced when they are most salient to the programmer.
Relatedly, although “lies-to-children” can be an appropriate teaching tool, they also risk undermining the health of the community by creating distance between those who know the full truth and those who have only been taught the “lie”. This principle helps minimize that risk, through the expectation that progressive disclosure not invalidate the programmer’s prior understanding of the language.
Finally, this principle helps make Carbon code easy to read, understand, and write, by minimizing the amount of Carbon knowledge that a programmer needs in order to read, understand, or write a given piece of code.