Earendil said:
I've seen a few "Those are major bugs! This will take a lot longer to get out the door!!" comments. It should be pointed out that the severity of the bug doesn't relate to how hard or easy it will be to fix.
A bug that trashes your hard drive, grows an AI, and takes over the world may be a very simple fix (assuming you fix it before it takes over the world). While a bug that causes an unwarranted beep in 2% of the programs, on 2% of the machines, could take forever to pinpoint.
Ask any program how many lines of code it takes to bring a program to it's knees, and how changing a single character can often times fix it 😉
In my limited experience while learning C++, it is FAR easier to pinpoint larger issues with a program, because those are the ones you're used to dealing with 🙄
It's the damn little nitpicky ones that make no sense at all, and the ones you spend forever and a day past when HW is due trying to fix 😎 😀
So just because Apple has some "Major" bugs to work out, doesn't mean there isn't a programer fixing it with literally his single hand in 5 minutes.
~Tyler
Exactly....
here is an example of one in Panther...
netstat -r
netstat: kvm_read: Bad address
netstat: kvm_read: Bad address
netstat: kvm_read: Bad address
netstat: kvm_read: Bad address
netstat: kvm_read: Bad address
netstat: kvm_read: Bad address
netstat: kvm_read: Bad address
netstat: kvm_read: Bad address
netstat: kvm_read: Bad address
netstat: kvm_read: Bad address
netstat: kvm_read: Bad address
netstat: kvm_read: Bad address
netstat: kvm_read: Bad address
netstat: kvm_read: Bad address
netstat: kvm_read: Bad address
netstat: kvm_read: Bad address
netstat: kvm_read: Bad address
seg fault.
Apple doesnt even plan on ever fixing this under Panther. We were told that they wont fix it until Tiger.