Linked by Thom Holwerda on Tue 19th Nov 2013 23:28 UTC, submitted by Anonymous
General Development

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.

Thread beginning with comment 577218
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: My problem with UEFI..
by CapEnt on Thu 21st Nov 2013 16:19 UTC in reply to "RE: My problem with UEFI.."
Member since:

In this case, there is a logic explanation other than just random chance: the added UEFI complexity.

See, motherboards manufactures needs to maintain large product portfolios, with fast release cycles. Overburdened engineering teams is pretty much the norm in this industry.

The BIOS is a far more simple kind of software, adapting it to new products is far more trivial than with UEFI. And even with BIOS, there is bugs, lots of it.

Most manufacturers took near a decade just to deliver a descent ACPI implementation, let's not even speak about slight more complex stuff, like virtualization support, hot-swappable storage, USB mass-storage boot, RAID, decent PXE support... and goes on.

Now, the manufacturers needs to mobilize their already spread thin engineering teams to adapt UEFI code, what is, in effect, almost a operating system by itself. The final result is obvious: far more bugs, in particular for cheaper low-end motherboards, that gets lower development budgets.

UEFI is one of these things that looks gorgeous on paper, but in practice it is a invitation to a disaster.

I'm pretty sure that most implementations out there is so screwed up that every single one would be very easy to exploit if you can override the operating system safeness. I can even point a easy entry point: these applications to fully manage the motherboard from the OS.

Reply Parent Score: 4