> That said: 15 years of activity is a lot of work to unpack in "specific terms", so "unspecified terminology" that still provides a rough overview it is.
How about list of open firmware(preferably consumer grade, big corps can get it anyway) that you helped or developed?
And if it is so good, why more and more hardware needs closed firmware?
The relevant firmware project to answer here is coreboot: My contributions range from technical contributions (see git log, ~3.5% of commits are mine, as poor a benchmark as that is) to support in our forums to documentation to behind-the-scenes work that keeps the community together or pushes back against even more blobs.
As for "why more and more hardware needs closed firmware": In 2005, which PC started from open source firmware, outside select data center deployments?
How about list of open firmware(preferably consumer grade, big corps can get it anyway) that you helped or developed?
And if it is so good, why more and more hardware needs closed firmware?