> What makes Framework's design different or superior to Apple in this regard?
1) You can change your IO as standards change or as your workflow changes
2) The point of failure for IO is at the point where the cable plugs in and creates stress, this point of stress is now separate from the mainboard - like in a desktop you have 20 pin USB ports on the motherboard that you wire your case up to - yeah that port could fail but it is far less likely to
3) If the mainboard IO fails you don't also have to replace your storage, wifi, ram etc
Is that really different from dongles? Since you can't buy them from third parties (yet), it sounds like they're just selling you your ports. Even Apple doesn't do that anymore.
Stress is also negligible, or TB ports are not fragile. We have a few thousand MacBook Pros and almost no mainboard replacements are due to port damage. This doesn't make Apple better, just noting.
Fair enough, but we've had no cases of TB controller failure that weren't covered under warranty. Framework's warranty as-is is insufficient for enterprise or commercial adoption. Swappable RAM, wifi, storage, etc are not unique to Framework (and Framework is more limited in internal ports than many older devices).
1) You can change your IO as standards change or as your workflow changes
2) The point of failure for IO is at the point where the cable plugs in and creates stress, this point of stress is now separate from the mainboard - like in a desktop you have 20 pin USB ports on the motherboard that you wire your case up to - yeah that port could fail but it is far less likely to
3) If the mainboard IO fails you don't also have to replace your storage, wifi, ram etc