segbrk

Not really. Of course it has pelican benchmarks in its training data. It likely has every article linked on HN in its training data. But that doesn't mean it was "trained on" the benchmark, as in specifically fine-tuned to make a better pelican. It just "knows" that the request is a benchmark.

Yes, but unless they support NVLink (they don't), it's quite slow.

That’s exactly why it could continue indefinitely. A war with no goal can’t be won. Nor can it be abandoned without bruising powerful egos.

Funny, my impression of KDE in the 3 and 4 eras was “Wow, this is shiny and sleek— oh, and it crashed. Nevermind.” Nowadays there is nothing I would recommend more to the average user who just wants something normal that works. It just works. What you’re saying just sounds like a pointlessly personal and ideological attack. Against a piece of software. Why?

Since that page is a little dense, the higher-level version: PCI supports Option ROMs (OpRoms) - plug in device like a NIC or a GPU, your BIOS actually loads compiled code from it and executes it on the CPU. In many systems for example PXE booting (net booting) is actually a function of the NIC, executing code on the CPU to load an operating system. We're talking actual x86/x86_64 machine code here running in the privileged pre-boot environment. Not portable or secure in any way. OpRoms _may_ now be checked for SecureBoot signatures on systems where that's set up properly at least.

EFI ByteCode (EBC) is meant to help at least the portability side. I'm not sure if anybody is actually delivering devices with EBC OpRoms yet though. I'm also not sure if anybody is looking at using the EBC VM to sandbox untrusted OpRoms.