|
Sounds to me like the vendor is in a win-win situation here, and the client is the (money) loser. The vendor releases buggy code, the customer (your client) pays a contractor (you) to fix it, you tell the vendor how to fix it, he includes the fix in his next release. Does he pay anyone for doing his debugging for him? I would think the client deserves some consideration in that case. --- <snip> --- On the other hand, if I have access to the source code, I can use my expertise to find the bug and kill it. I can then share the results of my efforts with the software vendor, who can QA my fix, and distribute it if appropriate. This leads to quicker results for me, cheaper and higher quality software for the vendor, and much more potential for high-quality code for all the vendor's other customers. Software development is not a zero-sum game --- with open source, everyone wins. +--- | This is the RPG/400 Mailing List! | To submit a new message, send your mail to RPG400-L@midrange.com. | To subscribe to this list send email to RPG400-L-SUB@midrange.com. | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.