I’m starting to see a pattern:
- Next week - Means Friday.
- July - Means last week of July.
- Up to 60w - Silicon lottery.
- …so, up to 80% capacity after 1000 cycles - Best case scenario.
It’s about MVP…minimum viable product.
Like…I don’t know man…if a display panel says max 400 nits…they usually can go around 410-420nits in the centre…all of those that reaches a customer. So, with Framework, this MVP thing isn’t exactly what I’d call striving for excellence.
Really, you can’t sell things (well, Framework can) base on ‘best’ case scenario and place that as product specs.
e.g. When Intel, for example, says X processor has a base clock of yGHz, and boost clock of zGHz…that applies to EVERY unit of that bin / SKU. Not the best case of that bin.
When an SSD is spec-ed as up to 1000MB/s sequential write…that ‘up to’ applies to all units if placed under the same ideal condition, not just the best SSD of the batch.
Framework really need to look at that 3rd 4th screenshot response you provided (above).
The concept of silicon lottery typically applies to unspecified behaviour or characteristic beyond documented specification. So, if “up to 60w” is documented, that’s considered in spec…for every unit sold, and should not be further subjected to silicon lottery. If I want more than 60w (undocumented), then sure, park that to silicon lottery.