Hm… Apache things are probably rather big, but I’ll have a look at least, haha.yeah go fix apache arrow for me please 😄
Have you tried running Python through Rosetta?
Did it?
Back in 2017 Intel announced it was dropping BIOS support in 2020.
![]()
Intel to Remove Legacy BIOS Support from UEFI by 2020
www.anandtech.com
EFI had some traction in the early 2000's but tried to leave BIOS behind.
![]()
UEFI - Wikipedia
en.wikipedia.org
UEFI was a adjustment to get more buy in but one of the offerings to get more buy-in was BIOS compatibility mode being required. 2005-2007 took a while for UEFI to settle down to very broad adoption. 2007 -> 2017 so 10 years to get to point Intel is willing to say going to turn transition mode off.
Kind of hard to dump odd-ball, 32-bit hackery when dragging it along in the basic boot mode of the system.
Yes, there is a solid, substantially large base of 64 bit code dating from around 2006-now . There is lots of more than 10 year old code out there to support as "legacy" and a substantial set of 15 year old code. There is large movement on some fronts , but on others there is a ton of hyper "ain't broke don't fix-it" , risk adverse folks out there also.
Yeah it’s hard to drop legacy when it’s in the boot process… So take it out of the boot process. Talk with MS, make PRs to LILO and GRUB, talk to the motherboard manufacturers and get rid of the crust.
As for old code, my take is this; If it’s a consumer or a networking machine run modernised, updated software. Otherwise that unpatched buffer overflow is going to hurt. If it’s an offline machine managing something like industrial machinery - it also doesn’t matter; Keep it as is. Don’t update the OS or the software and keep it on legacy hardware. There are still active production of 80186-like chips and PPC G3s; Low volume but it’s being made.