"NO WARRANTY" blah blah blah

"NO WARRANTY" blah blah blah

Posted Apr 11, 2005 2:32 UTC (Mon) by JoeF (guest, #4486)
In reply to: "NO WARRANTY" blah blah blah by NAR
Parent article: Protect Your Source Code: Obfuscation 101 (O'ReillyNet)

The "No warranty" clause is also very common in closed source. Have you ever looked at the Microsoft licensing agreement?
I just installed mapping software for my GPS (closed source, of course), and the producer (Garmin) has the same limitations of warranties etc. that you find in open source.
So, that's not quite what distinguishes open and close source.

I agree with your assessment, though, that obfuscating code makes it harder to provide support. That's why obfuscation can nowadays be done on a more or less automated basis, during the compilation process. An example is the product called dotfuscator, which, as far as I understand it, works on the bytecode level (MSIL, as the .Net bytecode is called.)

---

(Log in to post comments)