What’s unique about Jam is that it tries to keep the ergonomics of a C-like language while enforcing safety without a garbage collector or lifetime annotations. Its main differentiators are owned bindings with automatic drop, no undefined or implicit zero-initialization, no first-class references, and a C-ABI-friendly design that aims to make safe code the default even at FFI boundaries.
Jam is trying to be a safe systems language with C-like immediacy, RAII-style cleanup, no lifetime syntax, no undefined, and low-friction C interop.
Comments
What’s unique about Jam is that it tries to keep the ergonomics of a C-like language while enforcing safety without a garbage collector or lifetime annotations. Its main differentiators are owned bindings with automatic drop, no undefined or implicit zero-initialization, no first-class references, and a C-ABI-friendly design that aims to make safe code the default even at FFI boundaries.
Jam is trying to be a safe systems language with C-like immediacy, RAII-style cleanup, no lifetime syntax, no undefined, and low-friction C interop.