If I release it, you won’t get the same experience I get

In my Minecraft modding repository, I was refactoring build-tooling and created a program called jardiff to ensure new build tooling created artifacts with the same functionality as the old ones, even if they weren't byte-for-byte identical. For instance, the old tooling had a Java 8-compatible sourceset with classes, while the new tooling removed this sourceset and pasted the classes directly into each mod, compiling them alongside the rest of the mod using Java 25. jardiff detected this difference due to class file version numbers being visible in disassembly.

However, I decided that this change was acceptable as I no longer support Minecraft versions requiring Java 8. To maintain confidence, I modified the jardiff disassembler to consistently output the same class file version number. This allowed me to easily focus on specific differences without worrying about byte-level changes. Having the tool's source code readily available in my editor while using it is advantageous, as it enables me to customize and focus on the differences I'm looking for.

If I package jardiff as a single binary, the source code won't be visible, and I lose this flexibility. Adding a domain-specific language for custom filters may not be as convenient or intuitive to use compared to the existing tool's built-in features.