4 ms·
Because it's fun. I have my own ongoing decompilation/reverse-engineering project for a video game. As part of it, I've accidentally stumbled upon delinking, a
by boricj 2y ago
Because it's fun.
I have my own ongoing decompilation/reverse-engineering project for a video game. As part of it, I've accidentally stumbled upon delinking, a very niche and esoteric technique for slicing an executable back into object files. This turned into a two year side-quest to create and improve my own tooling for it, which has been by far the most interesting and intellectually stimulating project I've ever embarked on. It's steadily attracting attention (with some cool in-depth technical email threads with various people around the world) and recently it has even gained at least one active user.
Is there a rational reason why I've tackled this project? Absolutely not. It's completely bonkers, both in idea and execution. I've committed some wicked acts of heresy with it according to conventional computer sciences wisdom, like delinking code across platforms/object file formats and shoving it into foreign systems in spite of ABIs.
Sometimes people just have an itch to scratch. Mine is to take a chainsaw to executable files and make twisted chimeras out of the torn off pieces.