3 ms·

plus it's javascript for christ's sake? the best they can do is obfuscate it.

• readme 14y ago
  Obfuscation is more than enough to protect the code. You need only to make the cost of ripping it off greater than or equal to the cost of creating it. IP is so much more than the code. It's the concepts, the graphics, everything.
  • keefe 14y ago
    I don't think so at all,even without trying to reverse it you can inspect the DOM and debug the event flow etc. I think "construction is more difficult than verification" is a good adage for engineering. JS/CSS is transmitted in the clear and it should move towards open source, plus it's not hugely valuable. Now, if this guy was doing projects at work to do charting and then he decides to open source that on his own? Not cool, you need to make your personal projects clear to your employers to avoid this nonsense. That being said if it was just charts and it was my company and he managed to get press on it... I'd probably give him a bit of a lecture about it and then probably a raise and continue it as open source.
    • readme 14y ago
      I wasn't advocating for the company to use obfuscation. It's largely irrelevant in this regard. I was replying to the comment above mine which was left by someone who seems to think that obfuscated code is somehow less secure than compiled code. I agree -- if I was the boss in this situation the open source thing would be allowed to continue.
• mmahemoff 14y ago
  To the people who make decisions like this, it's all 1s and 0s. I mean literally there will probably be some policy pertaining to "software", or some manager freaked about "software" being released. No-one will stop to care about the deployment model when making this call.