These are the ideas that have been considered while creating the Operon-language:
- Language must be centered around the data.
- The data must be self-describing.
- Language must have a clear separation for getting the input, processing the data and sending the output.
- Handling the data must be as simple as possible.
- Language must be simple and consistent in its syntax and semantics.
- Language must be easy to understand.
- Language must be easy to extend.
- Language must stand the test of time.
- Language must be usable in real production scenarios.
- Terse code is more important than being able to display it visually, therefore low-code as tooling is not a goal.
- Language must have garbage collection.
- Runtime efficiency is important but not the end-goal.
- Being able to write code fast is more important than having blazing fast runtime.
- Static-typing is not important.
- Compile-time optimizations are less important.