Quote:
|
Originally Posted by Malleus Dei
Mal thinks all bugs SHOULD be fixed, and that all bugs CAN be fixed (leaving out those that are the result of design limitations - the 255 bug and such). I wish that I had the clout to insist that they MUST be fixed - because if I had it, then they WOULD all get fixed.
I fear we will see another under-documented adequacy patch and that legacy bugs will continue to pop up and bite us on our collective butt in the future.
|
I do think that may be a possible result - but not because Markus won't try, but because he 1. (has a limited amount of time to address V6 before he goes on to ITP and V7) and 2. (knows that the rewrite of V7 will better address some of these legacy bugs that will find resolution much easier in a new code base than continuing to patch the old one which could raise even more issues).
Some will see that as a "cop out" when in reality it's a good technical decision as well as a good business decision for the long term.
One other thing here.... every application has a "shelf life". Most major corporations replace the entire code base of an application every 5 to 10 years. The core OOTP V6 code base is six years old, and it's very likely due to be replaced. I think this was in part the reason to access the SI code - to give Markus a chance to build V7 on a clean slate. That too, is why spending too much time on V6 may not be in everyone's best interest.