> You wanna tell me that using a proprietary BIOS is better than using > Coreboot?
That's not what I'm saying. Sure, maybe there's less proprietary software with Coreboot installed but since Coreboot has adopted proprietary software to support these, proprietary software's still there either way. Making an argument that it's "better" than 100% proprietary isn't much of an a argument, I think, because the goal should be to find something that can be used without any proprietary software *anywhere.* 100% freedom, not 95% freedom or even 99.9% freedom. > Sure, it has some bottlenecks but you should agree that using a > completely-free (even by Mr.Stallman's merits) computer with some trouble is > better than buying a laptop, where you cannot get rid of the non-free BIOS no > matter what. Except that the Chromebooks don't fall into this category of being completely free: Coreboot has adopted binary blobs. Perhaps the free software community needs a Coreboot-libre, where someone saying that "it runs Coreboot-libre" would be a way to know that the device can be used in freedom. With the adoption of binary blobs, saying "it runs Coreboot" doesn't mean anything anymore. In addition, cryptographic signatures are in place to verify that these blobs are never modified. The addition of a crypto system makes things far more difficult so, if anything, such crypto signatures take us even further away from having freedom than a machine that doesn't use such a thing and has only binary blobs. I'm not saying binary blobs are any better - Either way you don't have freedom - but what I am trying to say is that this huge task of working to get freedom becomes even bigger, perhaps impossible, when strong crypto is added to the mix. > so I can recommend it to others If you're going to recommend something, it should be something that is actually possible to use in complete freedom in practive. While no means the only example, my ThinkPad X60s with Coreboot would be one example. In this case no binary blobs from Coreboot are needed.
