Draft HN reply explaining Office.js add-in vs VM/Wine
Session from pi-for-excel-sessions on Hugging Face by thomasmustier · MIT · condensed by Coders Talk
Click a segment to jump to that moment
2msession
0interventions
by library · 1d
GOAL
Research the Pi for Excel repo to answer a Hacker News comment asking why the project doesn't use a VM/Wine approach instead of a native-feeling add-in, then draft a reply.
- +0Prompt · +0Got a question on HN about this repo: why not use a VM/Wine for a native experience instead of the add-in approach?
- +0mAgent did · +0mExplored repo structure, README.md, and install docs, then grepped for mentions of wine/vm/native/Office.js/webview to understand the actual architecture (Office.js add-in, cross-platform, mkcert for local HTTPS) before answering.
- +0mAgent did · +0mDrafted an HN reply explaining the project runs inside native Excel via an Office.js add-in, and that VM/Wine would add overhead, licensing and reliability issues; offered a snarkier alt version.
- +1mPrompt · +1msjre (typo for 'sure')
- +2mAgent did · +2mProduced two ready-to-post reply versions: a neutral/technical one and a punchier HN-style one, both explaining the Office.js add-in approach versus VM/Wine.
- +2mOutcome · +2mTwo draft HN replies produced (neutral and punchy) explaining the Office.js add-in architecture vs VM/Wine.
VERDICT
I'd start by pointing the agent straight at the README and install docs since that's where the real architecture explanation lives, rather than letting it grep around first. Having it draft both a neutral and a punchier HN-style reply worked well and saved me from writing two versions myself.