It looks like you're either showing off your own ignorance of tools that enable workflows you can't imagine, or you're assuming that everyone's organization methods must resemble your own habits.

> Using proprietary connectors.

Not for the past decade; it's been no connectors for most products, but standard PCIe connectors for the Mac Pro, and NVMe over Thunderbolt works fine.

>> XHCI

> Not on Lightning.

Again, not relevant to any recent products. And I'm pretty sure you're misunderstanding what XHCI is if you think anything with a Lightning connector is relevant here (XHCI is not USB 3.0). You can connect a Thunderbolt dock that includes an XHCI USB host controller and it works out of the box with no further driver or software support. I assume you can do the same with a USB controller card in a Mac Pro.

>> AHCI

> How exactly would Apple not support AHCI?

This might be another case of you not understanding what you're talking about and are lost in an entirely different layer of the protocol stack. Not supporting AHCI would be easy, since they're no longer selling any products that use SATA, and PCIe SSDs that use AHCI instead of NVMe died out a decade ago. But as far as I know, a SATA controller card at the far end of a Thunderbolt link or in a Mac Pro PCIe slot should still work, if the SATA controller uses AHCI instead of something proprietary as is typical for SAS controllers.

Only in version 2. WSL1 didn't run a Linux kernel, just provided binary compatibility to run Linux userspace programs.

I would love to see NDAs for trade secrets limited in a way that incentivizes companies to rely on patent protection instead, where the system is set up to ensure that knowledge eventually becomes public record and freely usable by anyone. It would be very interesting to see how eg. the tech industry would change if trade secret protection were limited to a meaningfully shorter duration than patents.

Regardless, making such a modification for personal use only would be hard for a copyright owner to win a lawsuit over even if they could find out about it. But publicly distributing your derivative work like this is definitely violating the original's copyrights.

Obviously all of that works better if Finder windows don't usually fill the screen, but it's not a hard requirement.

Multi-GPU has recently experienced a resurgence due to the discovery of new workloads with broader appeal (LLMs), but that's too new to have significantly influenced hardware architectures, and LLM inference isn't the most natural thing to scale across many GPUs. Everybody's still competing with more or less the architectures they had on hand when LLMs arrived, with new low-precision matrix math units squeezed in wherever room can be made. It's not at all clear yet what the long-term outcome will be in terms of the balance between local vs cloud compute for inference, whether there will be any local training/fine-tuning at all, and which use cases are ultimately profitable in the long run. All of that influences whether it would be worthwhile for Apple to abandon their current client-first architecture that standardizes on a single integrated GPU and omits/rejects the complexity of multi-GPU setups.