Wax
waxlang.dev- Category
- Developer Tools
- Rank
- No. 2380Tools index
Previous survey · No. 2272 ·
- Type
- TOOL
- Use case
- Software Testing & Quality
- Interfaces
- Web · CLI · API · SDK
- Date
About
Wax is a language for deterministic recording and replay that lets developers restore any recorded frame of a running program and execute new code against that past state to inspect, query, or change what happened. This showcase demonstrates the concept using a real Doom playthrough, rewinding the recording, extracting data Doom never logged, and replaying the run under altered rules (e.g. one-hit enemies, health-costing bullets).
What it does
Wax's own site describes it as a system for recording a running program and later restoring any frame of that recording, then running newly written code against the restored state to surface information the original program never logged, and to replay history under changed rules.
Stated on the product site
- Recording contents
- A recording stores restorable game state and the input tape rather than a video capture
- Investigation mechanism
- Queries read the complete state at a single restored frame and return a typed result, which an investigation then correlates across the whole run
- Access surface
- Recordings can be opened either in a Wax Inspector tool or through recording APIs built into other tools
- Demo component licensing
- The Doom engine port used for this showcase is licensed separately from Wax itself, under GPLv2
Not stated on the site
- The page does not say what language or runtime the query functions used for investigations are written in.
- It is not shown how a recording session is started or bounded in a user's own program outside of this Doom demo.
- The page does not indicate current availability or terms for trying Wax on a project other than this showcase.
Written from the product site at waxlang.dev.
What it can do
Record a deterministic execution of a running program
Running program (e.g. Doom session) → Recorded execution trace
Rewind and restore any recorded frame of a running program
Recorded execution trace → Restored past program state
Execute new code against a restored past state to extract data never originally logged
Restored program state and query code → Extracted/inspected game data
Replay a recorded run under altered rules or modified code
Recorded execution trace and modified rules/code → Altered replay of the run
Tags
Media
Comments (0)
No comments yet
Editorially curated, with community endorsements as a secondary signal. Corrections welcome.