I apparently have a very uncommon viewpoint on this, given the flavor of the comments.

I won't try and say that this situation is totally fine, or ideal, or anything close to it, but I think that in order for us to know how to feel, we need one very important piece of information that is missing: was the actual BIOS update itself bad in some way, or was this just the kind of error that happens sometimes, especially as hardware ages.

If it was the former, then this becomes quite bad: Framework released (even if they were not the ones who made it) a software update that bricked someones computer, and it is incumbent upon them to fix it, even out of warranty.

If it's the latter, then, I'm sorry, but that's the kind of thing that happens sometimes. Yes, having dual bios chips or some other way to recover from a failed flash would be nice, but I don't know the engineering trade offs to make that happen. Lots of desktop motherboards have it, where space is not at a premium, but do any laptop motherboards have it? My guess is that, at the bare minimum, it's much much less frequent.

I think that, in the latter situation, the main thing that I would like to have seen from a company like Framework, with their ethos, is to provide the pogo pin reflashing tool (at a reasonable price), along with the necessary instructions and files, either for the user, or for a local, inexpensive computer repair shop (depending on the users preference). So even in the latter situation, I do think that Frameworks support is lacking here. This seems like the kind of thing that, with the proper tools (which seem cheap) and instructions and files, that this wouldn't actually be that hard, especially for the type of consumer that would buy an upgradeable, modular laptop.

But, in the case that the BIOS itself was not bad/caused the bricking, then I think the rhetoric around this is overblown. I'm not sure that any laptop I've ever had before has ever told me that I needed a bios update (aka: provided that level of support post purchase).

Again, if the BIOS was in fact bad, and caused the brick (and no, a thread of people who experienced the problem is not enough to conclude this), then that's a very different situation, and the level of failure exceeds even what is described here. And even if it wasn't bad, I don't think think that "buy a new mainboard" is the appropriate service response when "buy these $20 dollars of parts and tools, and follow this guide" would likely have solved the problem.

But, as I understand it, BIOS updates are always somewhat dangerous. If Framework is on the hook for every time a BIOS goes bad outside of warranty even in situations where nothing they did directly caused the issue, then what they will do is just stop offering BIOS updates outside the warranty window. We can hold two ideas in our heads at once: Are they completely and perfectly living up to their ideals? I think that the answer here is obviously, even in the least bad case, no they are not. But are they providing better service than other laptop manufacturers? I think that as long as the BIOS file wasn't bad, the answer is yes. No laptop manufacturer would have offered to fix this out of warranty if they even provided continued BIOS updates, and for most manufacturers, their answer would have been "buy an entire new computer", and your only alternative would be third party resellers or used parts on ebay to get a new motherboard.

-edit- After doing a bit more research, BIOS recovery paths in laptops, while not universal or as common as in desktops, are also not exactly rare, and not having one, in a company with Frameworks ethos and stance, is worse than I initially assumed.

I think that, even if this isn't due to a bad BIOS or updater (which, again, would make them, in my opinion, liable for fixing it), then this is a very significant oversight, and the fact that they don't provide the support necessary to route around it (reasonably priced tools and clear, well written instructions) is even worse.