In StarTree, there is a design principle that suggests using four-letter words with no drooping letters for the terms and APIs within the language. This paradigm aims to promote a specific naming convention and reduce the overall API surface by enforcing a consistent pattern. Here are the possible words which can serve as a head to a term within the base framework. These 4-letter words evolved after discovering the 5-letter word pattern first.
The idea behind this approach is to create a concise and uniform syntax throughout the language, making it easier to read, write, and understand the code. By limiting the term length to four letters and avoiding drooping letters (such as g, p, q, y, etc.), the language's vocabulary becomes more compact and streamlined. These words are also both noun and verb at the same time. It's surprising that we can model all of computation based on even just a small subset of such patterned words!
Adopting this naming convention can have several benefits. It reduces cognitive load for developers as they work with the language, making it easier to remember and recognize terms. It also promotes a more uniform and aesthetically pleasing code style, which can contribute to code readability and maintainability.
However, it's important to note that while this paradigm is encouraged within the StarTree language itself, it may not necessarily apply to custom DSLs built on top of StarTree. When implementing your own DSLs, you have the freedom to choose the naming patterns that best suit your specific domain or requirements.
Ultimately, the decision to adhere to a specific naming convention, such as using four-letter words with no drooping letters, depends on the goals, principles, and preferences of the language designers and the community using the language. It's a design choice that aims to create a unique and consistent coding experience within the StarTree ecosystem.