Minor note: dried pasta is made with semolina flour, not white flour & eggs like many fresh pastas are. It's still a refined (germ removed) ground wheat flour, though not usually bleached.

If there did, it'd be a distinguisher attack on that CSPRNG. So for a non-broken CSPRNG, the answer is "no", by the definition of "non-broken CSPRNG".

If it had a practical impact, then it would imply that such statistical tests could be used as a distinguisher to attack the RNG. They fail as distinguishers, even with absolutely enormous amounts of data, so the bias is too small to have any influence in any practical experiment. You'd expect to need to observe 2^128 states to detect bias in a 256-bit CSPRNG, which means you'll have to store 2^128 observed states. That's around 10^20 EiB of storage needed. Good luck affording that with drive prices these days!

Funnily enough they're toxic to all remaining dinosaurs.

Also join the Discordian society, and be a pope. You'll be a pope in the society anyway, whether you join or not, but it's more fun as a member.

There are fewer blue cones in the fovea centralis than there are in the surrounding parts of the macula, so humans can't resolve details as well in blue light.

The sensitivity of S cones is also simply much lower than that of the M cones. It's clear that pure (0, 0, 1) blue is perceived as vastly darker than pure (0, 1, 0) green. Blue light must be about 10x brighter (in linear intensity) than green light to be perceived as equally bright; the brightest full-saturation blue in sRGB looks about as bright as the very dark green (0, 0.1, 0). The contrast on black background is incredibly poor.

Which is why people who understand color tend to add a bit of green in to make a color which still looks deep blue but is much brighter than what #00f looks like

There is a phenomenon where I call things blue where my wife call things green.

Now reading your comment perhaps that's why? And some eyes would gladly distinguish green rather than blue?

AES is most often used in a streaming mode, where it's used to generate a keystream. AES alone is useless, it MUST have a mode of operation to provide any security. A streaming mode can then encrypt any number of bits greater than 0. AES-CTR is one of the more common streaming modes.

This is why I like the recent rise of cooperative board games. Clue is an older example, but there are more of them these days.

That's a ways out. We're not even using all bits in addresses yet. Unless they want hardware pointer tagging a la CHERI there's not going to be a need to increase address sizes, but that doesn't expose the extra bits to the user.

Data registers could be bigger. There's no reason `sizeof int` has to equal `sizeof intptr_t`, many older architectures had separate address & data register sizes. SIMD registers are already a case of that in x86_64.

> There's no reason `sizeof int` has to equal `sizeof intptr_t`

Well, there is no reason `sizeof int` should be 4 on 64-bit platforms except for the historical baggage (which was so heavy for Windows, they couldn't move even long to be 64 bits). But having an int to be a wider type than intptr_t probably wouldn't hurt things (as in, most software would work as-is after simple recompilation).

You can do a lot of pointer tagging in 64 bit pointers. Do we have CPUs with true 64 bit pointers yet? Looks like the Zen 4 is up to 57 bits. IIRC the original x86_64 CPUs were 48 bit addressing and the first Intel CPUs to dabble with larger pointers were actually only 40 bit addressing.