Have any of you looked at the list of licenses that are included in major packages? In any commercial OS? Pick your favorite app, click Help-About, and many times you'll get a nauseating list of patents, copyrights, and other licenses for technologies that make the app work. If disclosing IP in the apps in an office is required, using OSS isn't going to be any harder to document than trying to find the IP in some commercial product.
Some people even do it the other way around. 90% of my use of X is just as a way to start lots of terminals on my screen(s). My favorite is still/usr/X11/bin/xterm.
Slashdot Mirror
Have any of you looked at the list of licenses that are included in major packages? In any commercial OS? Pick your favorite app, click Help-About, and many times you'll get a nauseating list of patents, copyrights, and other licenses for technologies that make the app work. If disclosing IP in the apps in an office is required, using OSS isn't going to be any harder to document than trying to find the IP in some commercial product.
Some people even do it the other way around. 90% of my use of X is just as a way to start lots of terminals on my screen(s). My favorite is still /usr/X11/bin/xterm.
;)
X has its uses, you know.
Did you all see this article?
http://www.foxnews.com/story/0,2933,48567,00.html
It appears to be yet another article from Fox on the subject.
Chalk up one more developer (me) who has gone the other direction--giving up gui devel tools for command line versions.
:)
Bash + vim + make >= GUI+ IDE (IMHO