On Wed, Dec 4, 2019 at 07:37 Zahid Rahman <zahidr1...@gmail.com> wrote:
> I'm not talking of reverse engineering, my point is traceability. Sure you are--you specifically brought up decompiling, which is the first step of reverse-engineering. And in a jar with no debug info, or obfuscation, it's not the last step. (And not getting into external modifications to a jar which could happen during load.) If you can decompile code then if there is a problem then there is a chance > that you can trace it. With .exe or dll you cannot trace the problem. Of course you can--it's just software. It's how we used too develop all the time. -- em: davelnew...@gmail.com mo: 908-380-8699 tw: @dave_newton <https://twitter.com/dave_newton> li: dave-newton <https://www.linkedin.com/in/dave-newton/> gh: davelnewton <https://github.com/davelnewton> so: Dave Newton <http://stackoverflow.com/users/438992/dave-newton> bl[0]: Bucky Bits <http://buckybits.blogspot.com/> bl[1]: Maker's End Blog <https://blog.makersend.com> sk: davelnewton_skype
