Systems Language

NovaC (L1)

5× better than C. Systems programming without segfaults. Compiles to native code via KYRx IR.

Why NovaC?

C is fast but unsafe. Every buffer-overflow, double-free, and use-after-free is a potential security breach. NovaC keeps C's performance and simplicity while adding memory safety via KYRx's region system.

It's the language KYRx compiles to internally. It's also what systems programmers write when they need control without fighting a type system.

NovaC vs C

Feature	C	NovaC
Buffer overflow	Possible	✓ Prevented
Use-after-free	Possible	✓ Prevented
Double-free	Possible	✓ Prevented
Manual memory mgmt	✓ Yes	✓ Yes (with regions)
Performance	✓ Bare metal	✓ Bare metal
Syntax familiar?	✓ Yes	✓ Yes

Region-Based Memory

// Traditional C (manual malloc/free)
char *buffer = malloc(1024);
strcpy(buffer, user_input);  // ← buffer overflow risk
free(buffer);

// NovaC (region-based)
region req_ctx {
  char buffer[1024];
  strncpy_safe(buffer, user_input, 1024);  // safe
  // freed automatically at region end
}

Use Cases

Kernels & bootloaders — direct hardware access without unsafe{}
Embedded systems — fixed memory budgets, deterministic deallocation
High-frequency trading — nanosecond-level timing, no GC pauses
Drivers & firmware — memory-safe, cryptography hardware control

Status

Target: Compiler implementation complete by 2026-06

Use: Internal (KYRx compiles through NovaC IR)