Right, Mozilla was actually first on the block with this. And even when they removed it it was available as an extension, because their extension ecosystem was capable of UI-level changes.
The media is terrible about reporting on "maximum sentences". The federal sentencing guidelines are super complicated and lazy journalists usually just add all the maximum numbers up and write these egregious numbers. In reality, a lot of the charges are deduplicated, can be served concurrently, or are automatically attenuated by factors like being a 1st time offender.
Might I suggest that instead of linking to the article at theatlantic.com you instead link to the archive.org archive of it? I couldn't visit it due to Cloudflare thinking IPv6 is the devil and then still couldn't read it due to the paywall. Here's the archive.org link that sorta works for me, until their JavaScript removes the majority of the page content shortly after loading:
Yep, there are still server CPUs with only P-cores.
They are a bit expensive but I wouldn't expect them to drop these skews in the long term for HPC & compute bound workloads. My guess is that diamond rapids will also have some P-skews and maybe AP skews.
