|
Marc Clifton wrote:
So, how do you address these concerns with a closed source commercial library? How do guarantee maintenance, security, defect resolution, etc?
Commercial libraries are there to make money. As such they are more likely to police their code and give you are more feature rich and dependable product since it does mean their paycheck. In open source, you are usually at the mercy of programmers that are working on the project in their spare time as they have a job somewhere to pay their bills. While not all open source fit into this mold, many do and the projects can take forever to complete and fix when errors arise.
Of course, there are commercial products that people put out and then seldom maintain, but you are more likely to have issues resolved and a stable dependable solution with a commerical product. And you usually have a support avenue when problems do creep up.
My first thoughts on this poll were more in the lines of integrating the open source into my project than actually using a library that is more of a black box structure.
An additional problem with open source is when they decide they are going to market it as a commercial application and then take your rights to it away or sometimes all future versions.
Rocky <><
www.HintsAndTips.com
www.MyQuickPoll.com - 2004 Election poll is #33
www.GotTheAnswerToSpam.com
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
