Assembler inserts are only available to professionals, and thus only large software vendors (software) can afford to use the work of such specialists. Before you write your program, start to distribute it, a good programmer thinks about the likelihood of cracking and sustainability of the program to him. Here we have to speculate a bit. Each program has some value, and what it more valuable, the more likely that someone will try to modify it. The programmer is on the one hand the barricades, a hacker on the other.

As programmers, who initiated, they ask the pace of play. Appears protection is a time-and hackers are a means to hack, written guidance on this matter, and protection is gradually losing its effectiveness. If the developer has worked on sustainability programs to hack, then the time in during which there will not be compromised copies increases. Here we encounter the double-edged sword: on the one hand, protection should be as efficient and simpler in its lifetime, on the other, it will still be opened for the final time. So before you start to protect the distribution, it would not hurt to think about the value of the program, setting its position in the market, etc.

Here it is impossible to give generic advice, but give you an example: one program costs $ 100, and the other similar to it, for free. Then, of course, a normal user will use free software instead of paying $. But on the other hand, not everyone will know about the existence of competitor, and then have to buy a license.