11–20 of 154 posts
I have no time to go through the thorns and landmines over incompatible systems or buggy system software tools from Apple as described by the blog post.
Again, I will wait until the software on Apple Silicon is mature and the developer ecosystem catches up to it which by then I'll be getting an M2 or M3 based Mac.
Same, or similar behaviors with the 2020 Intel MBP. I ended up having to format the drive as an exFAT drive and then reformat again as APFS to get it to reinstall it was a real pain in the ass.
But at least with an intel Mac you can boot in target mode using cmd - t and then clone/mount/erase/whatever the disk from another Mac! Instead with ARM you can’t mount the disk as an external drive. That’s why this mess started!
P.S. T2 Macs are actually the most difficult to restore to the latest OS sometimes. The installer is anal about asking local password, booting from external USB, etc. and you might end up having to go through internet restore once and then upgrade the OS. M1 is actually an improvement and simplification from clean OS install perspective.
>Uff…what a paintful process! If an issue takes less than 5 different attempts to resolve and under 1-2 hours to fix, that can't really be called painful, merely annoying. Especially when it's only a one-time problem.
If your bar is "It just works", then for me at least, if it takes me more than 1 minute I'd describe it as painful. My mother would describe anything that's not immediately obvious as painful.
>Uff…what a paintful process! If an issue takes less than 5 different attempts to resolve and under 1-2 hours to fix, that can't really be called painful, merely annoying. Especially when it's only a one-time problem.
When the resolution means that you need another Mac at hand it is not merely annoying if you don't.
>Uff…what a paintful process! If an issue takes less than 5 different attempts to resolve and under 1-2 hours to fix, that can't really be called painful, merely annoying. Especially when it's only a one-time problem.
Why not just do the usual dd if=/dev/zero of= bs=1M count=1024 instead of using those weird proprietary tools?
This option is horrendously inefficient on most modern drives. For many SSDs, issuing a secure erase request is an almost instantaneous process as it only requires the drive to generate a replacement encryption key, and need not even entail bulk writing or erasing physical flash pages
Why not just do the usual dd if=/dev/zero of= bs=1M count=1024 instead of using those weird proprietary tools?