Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://kitty.haus/users/lamp" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>lamp</span></a></span> yes and no.</p><p>Yes, <a href="https://infosec.space/tags/Apple" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Apple</span></a> <em>will</em> <a href="https://infosec.space/tags/EoL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>EoL</span></a> the <a href="https://infosec.space/tags/Intel" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Intel</span></a>-based <em>"Cheesegrater"</em> <a href="https://infosec.space/tags/MacPro" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>MacPro</span></a> by 2029-2030 as per their preannounced platform lifecycle of 10 years.</p><p>No, because <a href="https://infosec.space/tags/Apple" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Apple</span></a>'s <a href="https://infosec.space/tags/ARMv8" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ARMv8</span></a>.1-A - based <a href="https://infosec.space/tags/SoC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SoC</span></a>'s are heavily modified in that they require a feckton of <em>custom chips</em> solely for the purpose of <a href="https://infosec.space/tags/ReducedLifecycle" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ReducedLifecycle</span></a> and making repairs harder if not impossible to facilitate...</p><p>Unlike their <a href="https://infosec.space/tags/amd64" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>amd64</span></a> / <a href="https://infosec.space/tags/EM64T" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>EM64T</span></a> - predecessors they don't have a dedicaded <a href="https://infosec.space/tags/EFI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>EFI</span></a> chip with "<a href="https://infosec.space/tags/BridgeOS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>BridgeOS</span></a>" aka. <a href="https://infosec.space/tags/AEFI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>AEFI</span></a> aka. <em><a href="https://infosec.space/tags/macOS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>macOS</span></a> - <a href="https://infosec.space/tags/Recovery" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Recovery</span></a></em> on but use the <em>exact same</em> <a href="https://infosec.space/tags/Flash" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Flash</span></a> chips that are <a href="https://infosec.space/tags/RAID0" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RAID0</span></a> as <a href="https://infosec.space/tags/SSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SSD</span></a>, and since those are custom with their own controllers ( <a href="https://www.youtube.com/watch?v=MANlo9fV9yI" rel="nofollow noopener noreferrer" target="_blank">based off info</a> from <span class="h-card" translate="no"><a href="https://social.treehouse.systems/@marcan" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>marcan</span></a></span> ) - basically every chip is it's own NVMe <em>but proprietary</em>...<br>And <em>when</em> (not <em>if</em>) they (inevitably) die (due to exceeding TBW lifecycle or <a href="https://www.youtube.com/watch?v=7cNg_ifibCQ" rel="nofollow noopener noreferrer" target="_blank">terrible engineering frying them with 12V on a 2,7V rail</a> ), the entire system is braindead.</p><p>And that is not <a href="https://www.youtube.com/watch?v=0qbrLiGY4Cg" rel="nofollow noopener noreferrer" target="_blank">by accident</a> but rather <a href="https://www.youtube.com/watch?v=RYG4VMqatEY" rel="nofollow noopener noreferrer" target="_blank">intentional</a>...</p>