howardshaw
Re:Show HN: A Cross-Platform ISO Editor (ISO9660/Joliet/UDF/Rock Ridge)
on Thursday January 08, 2026 @05:56AM (#46539599)
OP here. A bit more context: I built this mainly for packaging cross-platform release artifacts where ISO compatibility gets tricky (Unicode filenames, files >4GB, and preserving UNIX permissions).
The app can create new images and also modify existing ISOs (add/replace/delete files, then rebuild). It supports ISO9660/Joliet/UDF/Rock Ridge so you can pick a compatibility set that matches your audience.
I’d love feedback on real-world edge cases to test: mounting behavior across OSes, Unicode normalization, deep paths/long filenames, large directory trees, etc.
Show HN: A Cross-Platform ISO Editor (ISO9660/Joliet/UDF/Rock Ridge)
https://www.vioware.com/iso_editor.html
Hi HN, I built VIO ISO Editor, a cross-platform GUI app for creating and editing ISO images on Windows 10/11 and macOS 10+.Why I built it: I often need to ship release artifacts for users across different OSes, and ISO compatibility gets tricky fast (Unicode filenames, large files, UNIX perms, and “what mounts cleanly where”). I wanted a single tool that lets me author one image with the right...
Re:Show HN: DocBeacon – See how people read your documents
on Monday December 08, 2025 @07:40AM (#46191563)
author here. thanks for checking it out.
two quick notes that might help you evaluate it faster. 1 heatmaps and reader paths are built from session-level page transitions, not just aggregate views. 2 the viewer does not need an account, and recipients do not need to log in.
i would love blunt feedback on two things.
which signal would change your next follow-up step. drop-off points, re-reads, entry pages, or something else
what feels missing compared with how you personally review proposals or decks
happy to answer technical questions about the tracking model and how we deal with noisy sessions.
Show HN: DocBeacon – See how people read your documents
I built DocBeacon because of a small moment that stuck with me. About a year ago, during a routine catch-up with our sales team, someone joked that most proposals vanish into silence after we send the PDF, and we end up calling blindly. Everyone laughed, but the frustration was real.When I later decided to build something of my own, this was the first problem I came back to.There are...
Re:Vibe Coding Is Too Much Cognitive Load
on Thursday November 20, 2025 @08:20AM (#45992277)
i get the appeal of vibe coding, but in practice it often shifts the hard work instead of removing it. you write less code, but you spend more cycles reconciling what the AI produced with how the system actually works. for small experiments it’s great, but once a product has real users, the cognitive load comes back with interest. the speed is real, but so is the debt.