[yjftsjthsd-h]

I guess, but the "whole concept of the machine" that I'm typing this on was to run Windows... 7 (I think?); that's a completely artificial limitation, as shown by running Ubuntu on it years after the hardware went out of support.

[sixstringtheory]

I'm not sure what the problem is, then. You have a device that does what you (or the GP) want, which is to install any operating system, tinker, etc.

Is the worry that Apple and its practices will dominate the industry to the point that you literally will not be able to turn on your current machine and use it?

[AsyncAwait]

> Is the worry that Apple and its practices will dominate the industry to the point that you literally will not be able to turn on your current machine and use it?

I know you're joking, but I actually kind of am...

Apple has a tremendous amount of industry influence, just see removal of the headphone jack.

[heavyset_go]

macOS deprecates support for Macs that are 5-7 years old with every release. I put Linux on them when new macOS releases no longer support them, and they're perfectly good machines afterwards.

When macOS deprecates support for these ARM Macs in 5-7 years, Linux isn't an option for them unless Apple puts in a lot of work to support a mainline Linux kernel on their hardware. Apple has said they won't support running other operating systems on these ARM Macs unless they're virtualized.

[coldtea]

>When macOS deprecates support for these ARM Macs in 5-7 years, Linux isn't an option for them unless Apple puts in a lot of work to support a mainline Linux kernel on their hardware.

Why would Apple need to "put a lot of work in"? Apple doesn't support Linux on 86 either. Third parties did the Mac Linux ports for 86, and will do them for the ARM Macs.

The only thing Apple needs to do is to not lock the ARM Macs from booting another OS, which is very easy to do -- Apple doesn't need to invest lots of work to run Linux on ARM Macs, just needs not to prevent it.

[heavyset_go]

> Why would Apple need to "put a lot of work in"? Apple doesn't support Linux on 86 either. Third parties did the Mac Linux ports for 86, and will do them for the ARM Macs.

Because ARM SoCs are fundamentally different than 32-bit and 64-bit x86 machines. The prime difference is the lack of an enumerable bus that even some ARM servers have, but are missing in ARM SoCs.

I bought an x86 Mac when they were first released and I was able to boot an Ubuntu live CD when I got it. No work was needed to get a mainline kernel running on a x86 Mac, but work was needed to support things like Apple's SMC and cameras etc.

> The only thing Apple needs to do is to not lock the ARM Macs from booting another OS, which is very easy to do -- Apple doesn't need to invest lots of work to run Linux on ARM Macs, just needs not to prevent it.

This is not true. Given the lack of an enumerable bus, someone will need to either fork the kernel and hardcode addresses for hardware, or someone will need documents to build out the DeviceTree. If hardware doesn't conform to existing standards, which nearly every ARM SoC follows their own, someone will need to do further work port the kernel to the machine. All the special deviations from standards that Apple baked into their hardware either needs to be documented accurately, or Apple needs to put the work in to get mainline Linux running on their SoCs.

This is a general problem in the ARM SoC and Linux space, and is not unique to Apple's SoCs. There are millions of ARM SoCs that are either stuck on old kernel forks because vendors never put the work in to get mainline Linux to support their SoCs, or they will never run Linux at all, ever. I don't even think all of the Raspberry Pi models have mainline support yet, and those that do only have it because of the work put in by the RPi Foundation, which has access to some vendor documentation, but I don't believe all.

To get an idea of the scope of the problem concerning Linux support on ARM SoCs, check out this presentation[1].

[1] https://elinux.org/images/a/ad/Arm-soc-checklist.pdf