XPost: comp.sys.mac.advocacy
From: nobody@haph.org
Alan news:10krnnr$2hee6$5@dont-email.me Wed, 21 Jan 2026
23:33:15 GMT in comp.os.linux.advocacy, wrote:
> On 2026-01-20 19:14, Gremlin wrote:
>> Alan news:10kp5t3$1mfma$1@dont-email.me Wed, 21 Jan
>> 2026 00:16:34 GMT in comp.os.linux.advocacy, wrote:
>>
>>> On 2026-01-20 15:17, CrudeSausage wrote:
>>
>>>> I just find it unfortunate that Anal is still replying to me. I am so
>>>> tired of his zealoty that I just put him in the killfile. No matter
>>>> what Apple does, it's always right in the minds of these people. Even
>>>> when their MacBook self-destruct when the TBW is reached, this is a
>>>> good thing.
>>> Still waiting for proof that:
>>>
>>> 1. SSDs die all at once because some storage locations die.
>>
>> If one of the NAND chips which together make up the SSD dies - the SSD
>> is done.
>
> So the whole CHIP needs to die.
Are you expecting half a chip? Maybe a quarter of it?
> Is that what actually happens?
Usually. Sometimes the NAND dies on it's own, other times the power control
IC is responsible for the failure. These aren't the only ways this result
can happen though. Apple has all kinds of ... interesting little circuit
designs under the hood that can fail in spectacularly catastrophic ways. I
don't know what their QC focuses on as much, but, I'm reasonably certain
it's not internal circuit design or layout. I don't think they care much
about that as long as it works - going by some of the things I've seen.
--
Liar, lawyer; mirror show me, what's the difference?
Kangaroo done hung the guilty with the innocent
Liar, lawyer; mirror for ya', what's the difference?
Kangaroo be stoned. He's guilty as the government
--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)
|
