Re:There is No Such Thing as Proprietary Client-side JavaScript
by ble on Wednesday December 28, 2011 @05:08PM
(#3401614)
Obfuscation is perhaps DRM, but a very specific subset of DRM.
Obfuscation: "I will provide a functional copy of my code that is not (human) reader-friendly; I want people to execute my code but present a barrier to extensive understanding or modification of its implementation."
When someone says DRM, I usually think of its least pleasant incarnations- platform lockdown software that must be installed to play a game or (interestingly) take a test, content that may only be accessed after phoning home and verifying that one is in good standing with the rights holder, etc.
To my mind, JS obfuscation protects IP in a way that more closely resembles compilation.
Re:There is No Such Thing as Proprietary Client-side JavaScript
by mmahemoff on Wednesday December 28, 2011 @05:53PM
(#3401770)
Well, I was referring to obfuscation as a means of protecting the code part, and DRM as protecting the content part. But true, it's a fine line between the two.
Obfuscation: "I will provide a functional copy of my code that is not (human) reader-friendly; I want people to execute my code but present a barrier to extensive understanding or modification of its implementation."
When someone says DRM, I usually think of its least pleasant incarnations- platform lockdown software that must be installed to play a game or (interestingly) take a test, content that may only be accessed after phoning home and verifying that one is in good standing with the rights holder, etc.
To my mind, JS obfuscation protects IP in a way that more closely resembles compilation.