# Resourceful Code Reuse: Challenges of decompiling overstated (pages 15-16)

**URL:** <https://forum.devtalk.com/t/resourceful-code-reuse-challenges-of-decompiling-overstated-pages-15-16/7911>\
**Category:** PragProg Customers\
**Tags:** suggestion, book-resourceful-code-reuse\
**Created:** [15 March 2021 21:45 UTC](https://forum.devtalk.com/t/resourceful-code-reuse-challenges-of-decompiling-overstated-pages-15-16/7911 "2021-03-15T21:45:41Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mikem3catsus](https://forum.devtalk.com/user_avatar/forum.devtalk.com/mikem3catsus/32/2597_2.png) [@Mikem3catsus](https://forum.devtalk.com/u/Mikem3catsus)\
**Post date:** [15 March 2021 21:45 UTC](https://forum.devtalk.com/t/resourceful-code-reuse-challenges-of-decompiling-overstated-pages-15-16/7911/1 "2021-03-15T21:45:41Z")

</div>

I feel the author has overstated the challenges of decompiling back to source as an IP protection mechanism. Certainly you won’t get as clean of code, but it isn’t going to hide IP considering everyone has access to both open-source and commercial decompilers like [uxmal/reko: Reko is a binary decompiler. (github.com)](https://github.com/uxmal/reko) and [Hex-Rays Decompiler – Hex Rays (hex-rays.com)](https://www.hex-rays.com/products/decompiler/), just to name two I found with a quick search.