A couple nights ago I was looking over the UEFI spec, and I realized it shouldn’t be too hard to write UEFI applications in Rust. It turns out, you can, and here I will tell you how.
Language gets me giddy, but thank god lots of other people get giddy over stuff like this.
You could write anything. But some of the first 3d party software for UEFI was malware like viruses.
Isn’t that you can write anything to boot it, that part is fine, its the fact that it adds complexity and leads to more failures, at least from what I’ve seen.
Being a repairman and system builder I tend to see more than your average Joe and what I’ve found is that screw ups that would simply require a CMOS reset in BIOS will leave a cooked board with UEFI. For example power here can often get iffy, with line sags and brown outs and while the BIOS boards will often handle it fine or at worse need a reset the UEFI boards? Tend to cook.
At first I just thought “Well its the new tech, DDR3, more cores, thinner traces, blah blah blah” but then I happened to get a hold of some Biostar and Asrock boards from the transition where pretty much the ONLY difference between board A and board B was that board A was BIOS and board B was UEFI and guess what? The BIOS boards are still going strong, the last of the UEFI systems will be brought back day after tomorrow and from the sounds of it it’ll be joining the others in the dumpster.
Now as to the “why” I don’t know,maybe there is a problem with the UEFI chips, maybe they just have insanely low tolerances, hell if I know, all I know is when I run out of BIOS boards I’m gonna end up having to buy spares of every damn board i buy because the UEFI ones just don’t seem to work as well, at least that is what I’ve seen,YMMV.