Hmmmm. Thank you bruno, thank ovnicraft, thank all. I understand this question, we all help me.
On 16 out, 14:45, bruno desthuilliers <[EMAIL PROTECTED]> wrote: > On 16 oct, 18:31, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > > > Hmmmm. > > The byte-code of Java and byte-code of dot.net are also not safe? > > Not even binary machine code is safe. Where do you think all these > cracked softwares come from ? > > Back in the mid-heighties, when Steinberg came to France to present > their brand new not-yet-translated-and-still-a-bit-unstable Cubit > (aka Cubase) software - which was quite heavily protected -, a couple > friends of mine where here with a cracked, translated, and *debugged* > version of it !-) > > The only physical protection for your code is to *not* allow access to > it in any form. IOW, a web application that *you* host. > > Now the question is who do you want to protect your code from ? As far > as I'm concerned, I won't even waste a minute trying to retro-engineer > a .pyc. > > > The best way to protected my code is a license? > > Apart from not granting access at all to the code in any form ? Yes. > That, and providing good quality software and responsive service for a > reasonnable fee - happy users will happily support you, and won't want > you to die, and unhappy users won't use your software for long > anyway. > > My 2 cents... --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
