This is true given a dedicated enough programmer. Since most programmers aren&#x27;t <i>quite</i> this dedicated, however, this isn&#x27;t 100% true.<p>From what I am aware, in lower level (C++) development there are some definite strategies to &quot;deter&quot; piracy even at a technical level. Stuff that Urs (developer of u-He software synthesizers) talks about here, eg:<p><a href="https:&#x2F;&#x2F;www.kvraudio.com&#x2F;forum&#x2F;viewtopic.php?f=4&amp;t=400768&amp;start=270#p5639387" rel="nofollow">https:&#x2F;&#x2F;www.kvraudio.com&#x2F;forum&#x2F;viewtopic.php?f=4&amp;t=400768&amp;st...</a><p>Basically:
A) Make the protective schemes as non-obvious as possible in a disassembler (obfuscation, making the copy protection part of some core routines etc.)
B) Provide a few obvious &quot;sweeteners&quot; that &quot;pretend crack&quot; the software for a period, but then show a &quot;whoops your copy is pirated here&#x27;s a offer to purchase it&quot; later. (EG: a time bomb.) This allows the crackers to get their 0 day warez thrillz, without actually truly cracking the program.<p>Of course, <i>none</i> of this is 100% insurmountable. That&#x27;s not the point of this exercise. The goal is to basically make cracking the software a chore more beyond usual, and therefore, not worth the typical cracker&#x27;s time.<p>I am not sure how one would approach this with managed software or web-wrapped software (although if you can run the copy protection in a native module, that would be the way to go.)