« Color-Challenged in Flash: part 2 | Main | Piracy, it's not just for breakfast: Part 3 »

Piracy, it's not just for breakfast: Part 2

To follow-up the Piracy-issue, another hot issue in regards to 'stealing' software, is decompiling and reverse engineering software & code. Using a decompiling tool one can potentially take someone else's piece of work and extract all kinds of info from it such as code, graphical items, sounds, etc... But ofcourse these tools can also be used on one's own files when for instance the source-files were on a crashed HD.

Recently there have been some interesting discussions on the FlashCoders mailing-list on these topics and a page on the FlashCoders Wiki has been created for this topic.


while software piracy is a real issue out there, people make too much of decompiled code that should really be the case.

for instance, what in your work, if anyone decompiles it, wouldn't you want them to see? is it the if...then...else constructs? is there anything really new (some methodology) of some sort you are using that you don't want copied? granted, there would be cases where people would have certain trade secrets etc that they might want to hide, though i think this is to the minimum.

the point really is, those who need such protection, would know how to go about protecting such works, otherwise, i doubt they would have the competence to create it in the first place. the other side of that coin is, those who would have the competence to extract such material, for the most part, can create such material. why go through the pain.

let's not forget that, unless someone is going to point me to a case in point (in which case it would still be rare), decompiled code cannot be used as-is. which goes back to knowing what to do with the code in the first place.

The fact is that no matter what language you code in, somebody can crack it. With Flash, it's just a lot easier.

But, in my opinion, the real value of code is the comments, because you need them to maintain and build upon the code.