A PDF tool that actually respects local workflows
What jumped out at me is not the PDF features themselves — those are useful, sure — but the way this repo is trying to become infrastructure for every surface at once: CLI, MCP, browser, desktop, REST, even an embed widget. That’s ambitious in a way I usually distrust a little. Most projects that promise “one engine, many surfaces” end up with one surface that’s clearly first-class and the rest feeling bolted on. Here, the pitch suggests the opposite: Rust core first, interfaces second. I’d want
papoo.work