|
I was going to add this but figured it might dissuade some people to vote 
cheers,
Chris Maunder
|
|
|
|
|
mostly for support code, like UI or non critical code.
all that makes our software is either home-made or use commercial source code ( e.g. dundas )
Maximilien Lincourt
Your Head A Splode - Strong Bad
|
|
|
|
|
Don't forget commercial producs can and do contian open source.
I used to work in the newspaper industry, on the printing side, everyone uses TIFF files I would say all products use the open source libraries from libtiff.org.
Now that is a mission critcal industry, any print problems equals no papers the next day!
"Home computers are being called upon to perform many new functions, including the consumption of homework formerly eaten by the dog." - Doug Larson
|
|
|
|
|
Don't forget commercial producs can and do contian open source.
For those who still use Internet Explorer, take a close look at the "About" box. You'll see a line that says something like, "Portions of this software are based in part on the work of the Independent JPEG Group."
So even Microsoft uses open source code. 
An expert is somebody who learns more and more about less and less, until he knows absolutely everything about nothing.
|
|
|
|
|
Maximilien wrote:
all that makes our software is either home-made or use commercial source code
And how do you know that the commercial source code, which you can't inspect, is up to par for your mission critical code?
Marc
Microsoft MVP, Visual C#
MyXaml
MyXaml Blog
Hunt The Wumpus
RealDevs.Net
|
|
|
|
|
in the example of Dundas, we bought the source code, so, we can inspect it.
When buying non-source code component, it's a risk, I agree, and it's kind'a of shared between us ans the component creator; if at some point the component does not work or is too buggy or hard to integrate in our product, we can change it, or contact them and discuss the issue with them and work together; it's for our mutual "bénifice".
Maximilien Lincourt
Your Head A Splode - Strong Bad
|
|
|
|
|
You can generally do the same with open source developers. In fact most of the ones i've dealt with have been more willing and able to help than their commercial counterparts where you generally have to go through a support desk rather than direct to the developer.
|
|
|
|
|
Actually, usually us in small parts only. Large open source projects usually are a pain to maintain in your code and I personally like to know my code I am selling, if it is a large part, I would not know the code and could be opening the project to security issues or defects.
Rocky <><
www.HintsAndTips.com
www.MyQuickPoll.com - 2004 Election poll is #33
www.GotTheAnswerToSpam.com
|
|
|
|
|
Rocky Moore wrote:
Large open source projects usually are a pain to maintain in your code and I personally like to know my code I am selling, if it is a large part, I would not know the code and could be opening the project to security issues or defects.
So, how do you address these concerns with a closed source commercial library? How do guarantee maintenance, security, defect resolution, etc?
Marc
Microsoft MVP, Visual C#
MyXaml
MyXaml Blog
Hunt The Wumpus
RealDevs.Net
|
|
|
|
|
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
