Firmware does change and often has security vulnerabilities, so you do need to be keeping it up to date the way you keep your OS up to date. Among other things, it includes processor microcode / errata fixes like some of the Spectre, Meltdown, etc. mitigations. It would be nice if we lived in a world where this doesn't need to change, but it does, and thankfully it is firmware and not hardware.
Presently they met Firmware, who was dressed in tattered rags and hobbled along propped on a thorny stick. Firmware said to them: “The Tao lies beyond yin and yang. It is silent and still as a pool of water.
It does not seek fame, therefore nobody knows its presence. It does not seek fortune, for it is complete within itself. It exists beyond space and time.”
Hardware and Software, ashamed, returned to their homes.
— The Tao of Programming, Geoffrey James, 1987
Or, in other words, any code which hooks directly to the hardware on one side and exposes abstractions (like an instruction set) that software can code against on the other.
I always assumed "firm" stuck, as in "You'll have a helluva time changing it, because it's the code that has to deal with all the complex electrical engineering stuff."
(E.g. processor errata, patched board mistakes via fuse or EEPROM, side effects of power supply undervolting or clock skew, or pre-initialized system murkiness)
* hard -> firm -> soft -> wet ware
https://en.wikipedia.org/wiki/Wetware_(brain)
Although this one is usually just referred to as the "user" ;)
But only because you pointed it out in your comment, thanks.
It's the newest thing, and it's going thermonuclear!
But then please introduce also the relevant variants of realtime (in analogy of hard, firm and soft realtime): vapor realtime and plasma realtime.
Cheers :)
https://github.com/hughsie/fwupd
It's integrated into recent distros, seamlessly shipping firmwares for supported vendors (Dell came first, HP arrived soon after, and I think I read Lenovo was being worked on) like this MS project does, or Apple has been doing for years.
Seriously though, being "hard to change" on some parts of the system can be a feature.
That may be a model suitable for a single machine. Once you get to hundreds, you get intimately familiar with how to update everything and how common firmware bugs are.
However, I can't help but think that this is yet another thing on NSA/FBI's wishlist to Microsoft, just as most of the tracking stuff in Windows 10 seems to be. Say hello to "targeted malicious updates" by the U.S. government.
Yes, I know this was probably possible with the Windows updates already, but I imagine the malicious firmware will be much less likely to detect = the agencies can use this against many more people.
In my mind, firmware is the low-level software that's embedded in a device, and is both hard to change and unlikely to need to change, because it provides utility foundational to using your hardware. How do you turn that into a service?
Edit: apparently I can't read because it was right in there: "Firmware as a Service optimizes UEFI and other system firmware for timely quality patches that keep firmware up to date and enables efficient development of post-launch features." So basically, take the limitations I mentioned and get rid of them.