Approximation is an important tool for compressing information into useable forms. All labels are limited approximations too. Such compression is inevitably lossy, but that is a sacrifice for the sake of practicality. The important question is what level of compression is acceptable for a given context. If I describe the location of a chess piece on the board, I don't need to specify how far off-center on its square a given piece is, so a 0-7 offset along each of the two axes is enough for game purposes.

When it comes to gender, I think we all agree that [0, 1] is insufficient, but how do we determine what is sufficient? Do we argue that a 2-bit vector (masc, fem) is enough to describe {neither, fem, masc, both} for rough rounding, or do we need more detailed values along those axes, or perhaps a third axis too (or more)?

Mine is #1B4D3E

Ayyyyy wanna smash bros?

I have PS2

Even if every single person in the world had a unique gender, you could store that in 33 bits

You can store that in a small QR code

lets burn down our civilizations by spending all our wealth discussing this

The issue is based on legal terminology. Gender isn't a legal thing only pushed into our vocabulary.

Allocate an unbound memory blob and sit back for the herd of the Rust coders to line up. Sell them a soda while they do their best chicken parody

So many other things are also non-binary, but people insist that not being 100% on their side means you're a million percent on the extreme opposite hateful wrong side.

There are 10 kinds of people in this world. Those who understand binary and those who don't.

My gender is e, which can be represented by neither integers nor floating points.

Maybe it can be represented by 1qbit

Obviously, there is True, False and FILE_NOT_FOUND

Choose one class of gender:

• Natural
• Rational
• Irrational
• Complex