Quote:
|
Originally Posted by sde wow, you're pretty defensive. just trying to have a conversation. you said those were encoders and you were doing obfuscation, which lead me to believe that by saying they were not a comparison to what you do, that they don't use obsfuscation.
you also did not address my obsfuscation vs encryption question. |
Which part of my response was defensive?
I'm not trying to prevent anyone to crack my code by applying encryption, I am trying to deter them by making it so time-consuming it is not worth it. This is why I not only obfuscate sensitive code, I actually write the application so that it is obfuscator-friendly.
Now, I don't get your overall point. Are you saying that if you have the possibility to make it difficult for others to steal your code, you shouldn't just because they can invest a huge amount of time and eventually break it open?
Another thing that you are not addressing here, is what sort of source code will you have when you have "cracked it". What names will you have to replace the functions, variables, classe names and others.
Have you ever developed large applications and maintained them over several years? If you have, you will understand how useless the code is once all comments have been removed and everything meaningful such as the defines used in case/switch have been replace with ridiculous names. How inviting is that code? I'd rather see USER_SETTINGS than something like _b915dcba1566493b. How well could the code stolen from you be maintained and commercialised by somebody else?
I repeat my yet unanswered question here: Why would you not obfuscate?