Darksoul71
8th June 2005, 18:44
Dear all,
it´s really sad to hear that Lightning UK has been forced to stop development on the famous DVDDecrypter. This tool has "earned" a place on my PC. Not solely for DVD Ripping purposes but mainly for burning and verifying ISOs. I can fully understand Lightning to cease development because it would cost his money and energy to continue the development and risk a law suit.
Once again this issue has raised my attention to a sad fact: Most freeware authors tend not to release the source code of their work. IMHO that is actually a bad thing. Why ? I´ll try to explain:
Once in a while we see applications staggering in development (e.g. when have we seen the latest update to DVD2SVCD, DVDShrink, etc). While the reasons for this are mostly fully understandable (the author of the program just doesn´t have the time any more, needs to earn money for a living), the reasons for not releasing the source code are mostly not obvious for me.
Software puts you as the author in a unique position compared to all other "physical" things we deal with every day: You can share your work with others without really giving something away ! Try sharing your car with thousands of other peoples and you get the picture. Now back to the reasons for "I don´t want to release my source code". To put it frankly: For me most of those reasons sound pretty ridiculous.
Just to name a few reasons I´ve heard and my comments:
"I´m not releasing the source code because some evil company could take my sources and include them in a ripping tools and sell them".
Comment: Well, would this hurt you ? No ! At least only in a moral aspect. You can be still confident and proud of your work. Even if this would suck, I guess you have still learned a lot during coding and I, personally wouldn´t care, if someone takes my sources for payware. If you have a problem with the financial aspect of selling a part of your work, I would suggest you sell either licenses of your code or sell the application itself (at least if you are confident enough that your work will pay off).
"I don´t want other peoples to see my ugly code !"
Comment: Well, if someone else doesn´t like your code, he should shut up and go on building his own application in what he calls "non-ugly" code. Personally I would rather like having a look at ugly code to see and learn how someone solved a problem instead of solving / developing everything new from scratch.
Ask yourselves, fellow developers:
Haven´t you learned a lot by looking at the code of other peoples ?
Wasn´t there often a small code segment / snippet from the source of another programm or someone sent you, that saved you fifty hours of work ?
Didn´t you experience problems where you wished to have a closer look into how Program <A> or <B> solved this ?
If you answer one or more questions with yes, then you should think about releasing your code if you haven´t already done so.
Want an example how open source could easily generate a new great application ?
Well, take the import module of AutoGK, mix this with the great resizing of FitCD, add a few drops of DVD Mastering with DVDAuthor, muxing with MPLex and burning with DVDDecrypter (or Nero) and there you have a good alternative to DVD2SCVD. All it would require would be the sources of AutoGK.
The source code release of DVD2SVCD could result in a new build which incorporates the RobShot-Bach-Functionality of DSBoba plus better resizing based on the FitCD sources ?!?
Please be aware that I don´t think that every freeware developer "owes" us his code. It´s the right of every individual to decide wether to release the sources or not.
Nevertheless, I tend to compare open source with a river head and the lifecyle of projects as the flow of the river. Some rivers never reach the sea (-> the project dies because of lack of interest, whatever), where as other rivers reach the sea and grow bigger. Does this metaphor match ? I think so, because without river head (read: Open Source) the river will never flow !
Sincerely yours,
D$
it´s really sad to hear that Lightning UK has been forced to stop development on the famous DVDDecrypter. This tool has "earned" a place on my PC. Not solely for DVD Ripping purposes but mainly for burning and verifying ISOs. I can fully understand Lightning to cease development because it would cost his money and energy to continue the development and risk a law suit.
Once again this issue has raised my attention to a sad fact: Most freeware authors tend not to release the source code of their work. IMHO that is actually a bad thing. Why ? I´ll try to explain:
Once in a while we see applications staggering in development (e.g. when have we seen the latest update to DVD2SVCD, DVDShrink, etc). While the reasons for this are mostly fully understandable (the author of the program just doesn´t have the time any more, needs to earn money for a living), the reasons for not releasing the source code are mostly not obvious for me.
Software puts you as the author in a unique position compared to all other "physical" things we deal with every day: You can share your work with others without really giving something away ! Try sharing your car with thousands of other peoples and you get the picture. Now back to the reasons for "I don´t want to release my source code". To put it frankly: For me most of those reasons sound pretty ridiculous.
Just to name a few reasons I´ve heard and my comments:
"I´m not releasing the source code because some evil company could take my sources and include them in a ripping tools and sell them".
Comment: Well, would this hurt you ? No ! At least only in a moral aspect. You can be still confident and proud of your work. Even if this would suck, I guess you have still learned a lot during coding and I, personally wouldn´t care, if someone takes my sources for payware. If you have a problem with the financial aspect of selling a part of your work, I would suggest you sell either licenses of your code or sell the application itself (at least if you are confident enough that your work will pay off).
"I don´t want other peoples to see my ugly code !"
Comment: Well, if someone else doesn´t like your code, he should shut up and go on building his own application in what he calls "non-ugly" code. Personally I would rather like having a look at ugly code to see and learn how someone solved a problem instead of solving / developing everything new from scratch.
Ask yourselves, fellow developers:
Haven´t you learned a lot by looking at the code of other peoples ?
Wasn´t there often a small code segment / snippet from the source of another programm or someone sent you, that saved you fifty hours of work ?
Didn´t you experience problems where you wished to have a closer look into how Program <A> or <B> solved this ?
If you answer one or more questions with yes, then you should think about releasing your code if you haven´t already done so.
Want an example how open source could easily generate a new great application ?
Well, take the import module of AutoGK, mix this with the great resizing of FitCD, add a few drops of DVD Mastering with DVDAuthor, muxing with MPLex and burning with DVDDecrypter (or Nero) and there you have a good alternative to DVD2SCVD. All it would require would be the sources of AutoGK.
The source code release of DVD2SVCD could result in a new build which incorporates the RobShot-Bach-Functionality of DSBoba plus better resizing based on the FitCD sources ?!?
Please be aware that I don´t think that every freeware developer "owes" us his code. It´s the right of every individual to decide wether to release the sources or not.
Nevertheless, I tend to compare open source with a river head and the lifecyle of projects as the flow of the river. Some rivers never reach the sea (-> the project dies because of lack of interest, whatever), where as other rivers reach the sea and grow bigger. Does this metaphor match ? I think so, because without river head (read: Open Source) the river will never flow !
Sincerely yours,
D$