Doesn't Apple support the major standard device categories: NVMe, XHCI, AHCI, and such, like most operating systems do? The challenges are all for hardware that needs a vendor-specific driver instead of conforming to a standard driver interface (which doesn't always exist). Lots of those can be supported with userspace drivers, which can be supplied by third parties instead of needing to be written by Apple.
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.
> Disclosing technical guarded and not publicly known technical know-how - I am ok with those.
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.
Nobody was trying to equate non-disparagement clauses with slavery. The relevance of slavery here is as an example of the kind of contract terms that everyone should be able to agree are rightly invalid and unenforceable. Any argument in favor of contract enforceability that would apply to a slavery contract just as easily as it applies to a non-disparagement contract is a bad argument, or at least woefully incomplete. Bringing up slavery serves as a necessary reminder that the details and nuance of the contract terms and their effects need to be discussed and argued, and that an unqualified "contracts should be valid" position is untenable and oversimplified.
The general principle is that you shouldn't be able to "sign away" something that's a constitutional or human right. Like the right to freely speak, the right to practice a religion, the right to be paid for work, and so on. Imagine if the severance contract specified that she had to convert to Islam in order to get her severance, or that she had to sacrifice a child. No court in the country would consider those clauses conscionable. Yet, somehow companies are allowed to gag your free speech as a condition in a contract? It makes no sense why this is allowed.
Everyone who has a job that requires them to speak for their employer signs away their “free speech” right to an extent. Your proposal would not lead to a tenable system.
This is legalized buying people off, yes these contracts ought to be illegal and the comparison to slavery (a worse, but same category of morally reprehensible power dynamic) is completely valid
That's theoretically possible but a bad idea for a managed switch, because they seldom have enough CPU performance or IO between the CPU and switch silicon to provide respectable routing performance. For an unmanaged switch, it's more likely that whatever CPU core is present (if any) doesn't have enough resources to run a real network stack.
Not exactly, but under US copyright law there is a limitation of exclusive rights that grants the owner of a copy the right to make an adaptation provided "that such a new copy or adaptation is created as an essential step in the utilization of the computer program in conjunction with a machine and that it is used in no other manner". Unfortunately, the law doesn't specify what "adaptation" means, and I'm not sure the concept of an "essential step" stretches to cover modifying your program to run on a new OS decades after its original host platform has gone extinct.
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.
Well, I claim that there is no violating of Original copyright whatsoever. The repository doesn't contain any of the contents of the original game disks or any of the files. You could argue that I used a small parts of the work, but that can only fall under https://en.wikipedia.org/wiki/Fair_use doctrine.
That's missing the aspect where exceptions to the ban can be granted by the DoD or DHS, so in practice the outcome will be that effectively all routers need to appease the national security apparatus before getting FCC approval.
The spatial Finder was something different: having each folder open a new window, and that particular folder's window always re-opening in the same position on screen, with the same window size and same layout of files inside. Having the position of each folder remain consistent and persistent allows you to remember a file's spatial location much as you would for a printed document on a physical desk (exactly where you left it), rather than having to recall its path in the file system hierarchy.
Obviously all of that works better if Finder windows don't usually fill the screen, but it's not a hard requirement.
With the classic OS, all the windows were supposed to work this way. And it seems most apps still do remember their window positions, making it easy to find them. (Expose even keeps the positions consistent when you 'zoom-out'.) Which is why Mac users tend to position their windows rather than relying on alt-tab or the dock or another app-switcher.
(IMO the spacial Finder was designed around floppies and small folders and didn't work so well with hierarchical folder views, so no big loss...)
As a general rule: any SSD benchmark that gives you a result of over 1GB/s is not measuring what's actually most important for day to day interactive use. And anything that's within a factor of two of the SSD's marketing numbers is probably relevant only to copying a single file to or from another SSD.
The Apple I was a pretty poor predictor of what mainstream mass-market computing was going to end up looking like. I don't think anybody has yet come up with the Apple II of local LLMs, let alone the VisiCalc or Windows 95.
Only in version 2. WSL1 didn't run a Linux kernel, just provided binary compatibility to run Linux userspace programs.
reply