This is true given a dedicated enough programmer. Since most programmers aren't quite this dedicated, however, this isn't 100% true. From what I am aware, in l

This is true given a dedicated enough programmer. Since most programmers aren't quite this dedicated, however, this isn't 100% true. From what I am aware, in lower level (C++) development there are some definite strategies to "deter" piracy even at a technical level. Stuff that Urs (developer of u-He software synthesizers) talks about here, eg: https://www.kvraudio.com/forum/viewtopic.php?f=4&t=400768&start=270#p5639387 https://www.kvraudio.com/forum/viewtopic.php?f=4&t=400768&st... 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 "sweeteners" that "pretend crack" the software for a period, but then show a "whoops your copy is pirated here's a offer to purchase it" later. (EG: a time bomb.) This allows the crackers to get their 0 day warez thrillz, without actually truly cracking the program. Of course, none of this is 100% insurmountable. That'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's time. 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.)