Opening Source: The Ultimate Customer Security Blanket
When Dan Appleman began to lose customers because companies had lost trust in third-party components, he gave them what they wanted: Source code. It's a controversial move with a long list of residual issues. Find out why Dan thinks it will all pay off.
by Daniel Appleman
March 22, 2004
ecently my company, Desaware, decided to release the source code for our component products—and in doing so found ourselves suddenly directly involved in the open source vs. closed source debate.
I suppose it's not surprising—along with privacy and intellectual property rights, open source will be one of the defining debates of this decade, the results of which will impact each of our careers (not to mention the profitability of corporations like Microsoft).
It's quick, easy and you get access to all the articles on DevX.
This registration/login is to allow you to read articles on devx.com. Already a member?
To become a member of DevX.com create your Member Profile by completing the form below. Membership is free!
Daniel Appleman is the president of Desaware Inc., a developer of add-on products and components for Microsoft Visual Studio. He is a cofounder of APress and is the author of numerous books including "Moving to VB.NET: Strategies, Concepts and Code," "How Computer Programming Works," "Dan Appleman's Visual Basic Programmer's Guide to the Win32 API," "Always Use Protection: A Teen's Guide to Safe Computing" and a series of ebooks on various technology and security topics. Reach him by e-mail .
ecently my company, Desaware, decided to release the source code for our component products—and in doing so found ourselves suddenly directly involved in the open source vs. closed source debate.
