Do you see any implications on PS3 sales, reputation, etc..because of...

[theprof00]

kowenicki said:

theprof00 said:
I just think it's funny that I try to look at the bright side by mentioning that they may go through the coding line by line and people jump all over me.
You don't know either. YLOD could be caused by several processors going idle, leaving one processor to handle everything. You have no idea, yet you are comfortable enough to insult someone else.

Seriously guys, chill out. For all we know, YLOD could be caused by a line of code simply saying "F" and the cell being confused by it. If a simple date problem can cause all this, maybe a programmer typed "teh cell" instead of "the cell" and it makes 'teh cell' go into overdrive lol.

there is a very big difference between some down time and this... stop with the damage limitation. its weak.

sony have already admitted that this could lead to some permanent data loss for instance.

I will stop when you stop calling this damage control. It's not. I'm just looking at the silver lining. I didn't know that suggesting potentialities was so looked down upon. What really confuses me is that while you condemn my hypothetical situation, you condone another hypothetical situation where Sony said

"as doing so may result in errors in some functionality, such as recording obtained trophies, and not being able to restore certain data."

MAY