FreedomLang is an AOT systems language compiling to libc/CRT-free x86-64 with OS-process-based concurrency and filesystem-visible job state.
Key Takeaways
Linux target emits ELF64 machine code directly via kernel syscalls; macOS emits AT&T assembly with -nostdlib; Windows emits PE/COFF assembly without CRT.
Concurrency uses real OS processes: fork on Linux/macOS, CreateProcessA on Windows; job inbox/outbox state is visible under FSABI paths on disk.
Hard split between world states (missing files, timeouts modeled as explicit data via with chaos) and bugs (out-of-bounds, bad tags terminate via fall/assert).
Compiler is readable JavaScript source run with Node.js, not a sealed binary; IR lowering and backends live in the repo with no LLVM path.
GC and heap exist across targets but macOS has the strongest path; Linux/Windows network/chaos parity and no-GC mode are still hardening.
Hacker News Comment Review
Only one comment so far: the choice of JavaScript as the implementation language for a libc-free native compiler struck at least one reader as unexpected, though the author frames it as a deliberate readability and auditability choice.
No substantive technical debate yet on process-per-job overhead vs. goroutines, the FSABI design, or the Windows PE/COFF backend.
