Cloth does not hide behavior behind runtimes or implicit systems. Execution is predictable, and the cost of every operation is visible.
Memory ownership is defined and enforced. Allocation, lifetime, and destruction are controlled directly by the developer.
Compiled with low-level control in mind, Cloth delivers consistent performance without sacrificing readability or structure.
Cloth is in active development. We are building the language, tooling, and ecosystem now, with room for future industry adoption and community-backed growth.
Most modern languages trade control for convenience. Hidden runtimes, implicit behavior, and layered abstractions make systems harder to reason about.
Cloth takes a different approach. Behavior is explicit, memory is owned, and execution is predictable. There are no hidden costs or invisible systems working against you.
It is designed for developers who need to understand their systems completely — not just use them.
Clear file structure. Explicit declarations. Predictable execution.
module cloth.examples;
import cloth.io.Out::{ println };
import cloth.collections.Arrays;
public class (string[] args) {
public Main {
hello() -> (error) {
println("An error occurred: " + error.message);
};
}
public func hello(): void maybe NullPtrException {
let greetings = [
"Hello", "Hola", "Bonjour",
"Ciao", "こんにちは", "안녕하세요",
"Chào bạn", "您好", "Hallo"
];
Arrays.iterate(greetings)
.foreach({ (i) -> println(i); });
}
}A Cloth source file is organized with a module declaration, imports, and a single top-level type. The layout is rigid by design.
Imports are precise. Bring in only the symbols you need instead of pulling an entire namespace into scope.
Values and return paths are declared directly in the source, making intent and behavior obvious at a glance.
A public Main class provides a clear and predictable program entry model for tooling, builds, and execution, entering in the constructor.