The most boring games you have Aver seen

Yesterday Claude built Snake and Tetris in Aver. I did not write the implementations. I reviewed the decisions. That distinction is the whole point. No if/else. No loops. No mutable state. No excep...

By · · 1 min read
The most boring games you have Aver seen

Source: DEV Community

Yesterday Claude built Snake and Tetris in Aver. I did not write the implementations. I reviewed the decisions. That distinction is the whole point. No if/else. No loops. No mutable state. No exceptions. Game loops through tail-recursive calls. Every side effect declared in the function signature. The games work. You can play them. But playability is not the point. The review loop is. What "boring" means here Here is the Snake game loop: fn gameLoop(state: GameState) -> Result<String, String> ? "Render, sleep, read input, tick — TCO recursive" ! [ Random.int, Terminal.clear, Terminal.flush, Terminal.moveTo, Terminal.print, Terminal.readKey, Terminal.resetColor, Terminal.setColor, Time.sleep, ] render(state) Time.sleep(state.tickMs) tick(readInput(state)) No surprises. You can see the intent (?). You can see every effect the function is allowed to perform (!). You can see the data flow: render, sleep, read input, tick. State goes in, state comes out. If this function tried to m