comparison · c_b8e80699547c (tommy-mor) vs c_a3b1b1967afc (tommy-mor)
Side A adds a substantial, working Reddit API client module with rate limiting, typed response models, and error handling that provides concrete, reusable functionality for the project. Side B merely deletes a planning document (PLAN.md), which is a design roadmap rather than functional code, offering no direct lasting implementation value even though it may reflect completed work described elsewhere.
Commit A adds a complete, production-shaped RedditClient (rate limiting, fetch helpers, and carefully deserialized Post/Comment types with helpers), which is lasting executable value. Commit B only deletes the PLAN.md design doc after it was finished, contributing no new code or bugfix.
Side A adds a substantial new Reddit API client with built-in rate limiting, HTTP request handling, structured response types, custom serde deserialization, and helper methods for working with posts and comments, providing reusable project functionality. Side B only deletes a planning document, removing design documentation without adding or improving runtime behavior.
comparison · c_a3b1b1967afc (tommy-mor) vs c_16438843de8f (tommy-mor)
Side B adds concrete, functional infrastructure: a working EventLog implementation (append/load with JSONL), a ViewStore for counting views with debounced disk flush, plus deployment artifacts (Dockerfile, fly.toml) and a deps.edn for test tooling. Side A merely deletes a planning markdown document with no accompanying implementation, providing no functional or lasting code value.
B adds lasting runtime and ops foundations: EventLog (JSONL append/load), ViewStore persistence, plus Dockerfile/fly.toml deployment. A only deletes PLAN.md with no implementation, tests, or behavioral change—cleanup after planning, not durable project value.
Side B adds functional project infrastructure and code: a JSONL-backed `EventLog` with append/load support, a persistent `ViewStore` that asynchronously flushes counts to disk, plus Docker and Fly.io deployment configuration. Side A only deletes `PLAN.md`, removing design documentation without changing runtime behavior or implementing any of the planned architecture.