antrozous wrote:
But then, in this case, I don't see what the problem can be. I know it's up to the Apple's tech team to figure it out, but I just don't understand what the problem can be...?
Lines of code. Thousands, if not millions, of lines of code.
Here let me cook up a little example:
* * * *
Let's say one of the lines in 10.6's wifi code, not a very important one, says "I love cake."
Cake, of course, is inherently insecure, so in 10.7, they changed that line to "I love pie."
Now, for most hardware, most of the time, this is fine, because they are looking for the code "I love <dessert>." Any dessert will do.
But for some pieces of hardware out there, certain wireless chips, or certain routers, or maybe just when certain pieces of hardware are combined, they are more picky, they look for "I love cake." But you updated to Lion, and suddenly, they can't find it. In a panic, your WiFi explodes killing millions.
* * * *
This is why any new piece of software, especially an OS, needs to go through a ton of testing on a variety of hardware and combinations of hardware. You just never know where little incompattibilities like this could pop up. Windows has a particularly hard time of this. There are tens of thousands, if not millions, of different possible Windows machines out there, and just as many peripherals. In Apple's case, I'm not quite sure how they missed this one, particularly since I am using all Apple hardware (iMac + Airport Express). In the past, there stuff has always "just worked," which is why I've been willing to pay a premium for it at times. I guess that's not true for me anymore.
But I'm not an Apple engineer, so who knows, maybe it was unavoidable.