When I said you, I didn't mean you guys in particular, I was using it in the global, when a programmer writes a generic program, one would hope they have the basic pipeline worked out so that upgrades can layer on top of the original code without changing the existing.
If a new feature is added to a server, that must be added to the client, true, but if the server doesn't use that particular feature, there should be no need to update it to be able to use it. It's like the ice maker in a fridge. Maybe you use it. Maybe you don't. You shouldn't have to re-install your oven if you decided to get a new fridge which may or may not have an ice maker. That's all I'm saying.
That rolls into what I was talking about with the 4 or 5 years comment. In my mind, the original opcodes should have been figured out and refactored to be as small as possible before release. Everything beyond is just icing, and will indeed need testing as it goes, but whatever happened to those original opcodes? If I'm understanding you correctly, they've been changed since release. Now, if I came back with my last project, and told the bank I sold it to that the network protocol was actually transfering twice as much as was required and needed to be changed, you can bet your ass I'd have a lawsuit on my hands, especially after 4 years.
|