The debugger is in alpha and currently supports local Windows x64 debugging with PDBs. The project also includes RAD Linker and a custom debug-information format, RDI. These components frame the project as a coordinated toolchain rather than a debugger-only release.
Thesis: RAD’s notable design choice is to pair a debugger with a custom intermediate debug-information format and a linker that can emit it. Mechanism: The README says PDB data can be converted to RDI on demand, while RAD Linker can optionally create RDI natively, avoiding that conversion step during debugging. Why now: The project overview makes the relationship between linking performance and debug-information handling explicit for teams working with very large executables. In described test cases where debug information spans multiple gigabytes, the project reports link times 50% faster; that is a project-reported result, not an independent benchmark.
First implication: Teams considering the tool should treat its Windows x64/PDB alpha support as the present boundary, and evaluate the linker claim against their own workloads rather than generalizing it. Evidence boundary: The supplied README does not establish independent performance validation, broad production reliability, or that planned Linux and DWARF support is already available. First watch condition: Watch for documented expansion beyond local Windows x64 debugging and for reproducible benchmark details across project sizes and configurations.