My point is more, “listening” is not the same as “changing things immediately”. It’s one thing to list out the problems with the Framework 16, but it’s another to be very confident that they point to an incorrect approach to gradually resolving those problems. Don’t forget, Batch 20 was still shipping out… four months ago? They’re up to supporting, what, six, seven different motherboards on the Framework 13? It’s not like they’re not busy.
And they are publicly acknowledging these issues and talking about them, too. See, for example, Framework’s software and firmware have been a mess, but it’s working on them - Ars Technica, from earlier this year. It does say something about relying on Compal to staff up to round robin firmware updates in the first half of this year. We’ll know whether they can find a groove, what, another year from now?
These things take time. Part of what I like about this thread is, people who don’t want to sign up for an early tinkerer’s computer with issues should probably steer clear of the Framework 16 for another generation or two.
It’s completely anecdotal, but my fans on my 11th gen FW13 are also fine – not saying it’s not a problem, but it’s hard to say what the problem is, or how Framework “should” respond. It depends… and I’m sure it’ll only improve over time, barring the occasional bug or regression. For the Framework 16’s the fan noise – the laptop pushes a ton of air, and I think that’s the idea. We’ll have to wait for hardware updates to deal with the high-pitched whining noise, and there’s not a lot to talk about until then.