@OpenComputeDesign @rl_dane
Okay no, UEFI absolutely does need to exist, it makes low level development go from rawdogging interrupts to just writing C code with the efi stdlib. Is the UEFI (edk2) code good though? No, hell, absolutely not. It feels like the code was made by a bunch of random university students without much of a coherent thought on anything.

I've attached two images of the VFR compiler source code (part of EDK2 BaseTools that I've been fighting with for the past couple of days), it's horrid. The styling is all over the place, barely any comments, a BUNCH of codegen (that happens to be incorrectly implemented so if you use more than 1 build job, you create a race condition with modifying the source *as it's being processed by the compiler* from which you get build fails once every 10 or so attempts that are HELL to debug without knowing what is happening), CRLF + NL mess (why do text editors on Windows even do this?!), dependencies from the freaking 90's with support for SGI workstations and more.

Oh yeah, if you've noticed, all of this was just for the VFR compiler, just a single dependency of EDK2. Onto EDK2 code itself - it's actually pretty decent!... as long as you only look at the base and not at edk2-platforms...