NeverMan -> RE: compressed transfert files... (11/20/2009 7:35:15 PM)
|
quote:
ORIGINAL: Jimmer quote:
ORIGINAL: Marshall Ellis Now, now, now! I'm not blowing off your posts! I do remember you orignally bringing this up but I cannot remember if you recommended a product? IF anything it's simply a memory issue with me so don't take it wrong if I run in a few circles! Yes, he posted a product (the same one, I think). The biggest issue is what he disparagingly mentioned here: A commercial product (EiANW, in this case) cannot use an unsupported product inside of itself (7zip, in this case). If 7zip is ever found to have a serious security hole, and the coders of 7zip could have left for greener pastures, Matrix would then be placed in an extremely precarious position: They would have to either remove the code or write/purchase other code to replace it. Either one would be unacceptable (to Matrix) in an already-delivered product. The former would require removing a critical feature. The latter would require that Matrix spend money without any possibility of recovering that cost from their customer base. Note that the problem is SUPPORT, not initial cost. Support ALWAYS costs something. Boiled down to the simplest possibilities, it either costs money (frequently referred to as "maintenance"), or it costs time (internal coder time spent fixing bugs in the external product), or it costs customers (customers who leave because a feature has been removed). End-users (such as the laughing-out-loud Neverman, for example) do not have this problem except in unusual circumstances. But, companies must factor in either money or risk. Since Neverman is still laughing despite the original logic I presented, perhaps an example would explain things: Let's say Microsoft decided that it wasn't making money on Office any more. So, they decide to make it public domain freeware. Naturally, since they would no longer be earning money off of sales of Office, they would not longer support the product. Now, as a typical consumer, this would be great for me: Office no longer costs anything. I'm not going to think about the future, because I can always download OpenOffice if Office craps out. But, a business looking at available office productivity suites would be hard-pressed to continue using Office. They may for a while, but eventually they would have to give it up. Now, go one step further and consider businesses who have used Office as a product vehicle. In other words, the company has created a product using Office inside that product (or as the runtime vehicle, etc), and they sell it. Can THIS company continue to use Office as their vehicle (unsupported)? Obviously, the answer is no. This last part of the example shows the heart of the problem from Matrix's perspective: Support on vendor-supplied products in saleable products is absolutely mandatory. AGAIN, why does the code have to go 'inside" the other code??? That's just ABSURD!! If the zip fails then a pbm file is produced... worse case scenario we are RIGHT back to where we started, worse case scenario.
|
|
|
|