Pairings

CPU + Operating System + Language + Function

This may be the best way to design a computer. The general public and a large part of the computing community have limited experience and exposure to alternate systems and designs. For the most part, the "pc" is an AMD64 CPU with a Microsoft or Apple system with an occasional Chrome book. Secondary systems are largely Linux based followed by the BSDs and other UNIX variants.

CPU architectures are more of AMD64, ARM64, POWER, SPARC64, MIPS64 followed by ZISC, OISC and digital signal processors among others.

I've done work with the UltraSPARC, PPC32, and AMD64 along with ARM32 and the standard x86 architectures.
From the basic design and application along with the original build system and developmental environments, I've come upon certain realizations.
OpebBSD was built on a SPARC system and is near perfect for scaling, databases and security.
FreeBSD is research based best ran on the POWER /PPC64  architecture and for research along with AI.

NetBSD is good for the ARM64  and input devices.

Form should always follow function with the programming-hardware combinations paired even to the level of language dependency for optimum performance.

Remember that there is no single standard. All standards and interpretations are acceptable as long as they honestly reflect from the truth.