just found some code that says "'endian': True"

someone needs to ban programmers from booleans

@foone what endianness is this?
"yes"
@foone In non-endian architectures, the bytes are just dumped in a big pile
@reedmideke @foone non-endian is where you just add up the bytes. Who needs numbers bigger than 510 really.
@foone if you set endian to false the numbers become circular
@foone ouroboros data type

@noiob @foone I suppose it’s better than

'endian': NULL

@foone Which is worse: using a boolean with unclear meanings for true/false, or using a pointer to a boolean so you can treat null pointer as a distinct third value?

@WLivi @foone imo the second, but it's close

the first can be fixed by renaming the variable, the second is just bad no matter what

but consider, the worst of both worlds

endian = null

@foone Too few programming languages support ternary, which means another bit to represent PDP-11 middle-endian encoding.

Or is that represented with the the seldom-encountered ‘endian’: maybe?

@foone I suppose endian: False indicates endian-free code
@jarhill0 @foone If the code needs to know the endianness, it's guaranteed to be wrong-endian.
@foone well, are the bytes endless?
@foone least obfuscated way to indicate a pure 8-bit CPU
@foone I was always partial to a three-way option myself. True, False, and File Not Found.
You just NEVER know when you'll need to tell somebody that you don't know if something was true or false because the file wasn't found. ESPECIALLY if you're on Windows where not everything is a file. 😇
@foone the one true byte order

@foone I’m more of an infinian myself

I say if the Halting Problem doesn’t let us determine if some bit of code will halt then NONE OF IT SHOULD, EVER

Take that, computer science

@foone There's gotta be a limerick or something that rhymes endian and boolean.
@foone `endian: false` would be beginnian
@foone Either that or Ian needs to watch out
@foone - Or maybe IDEs should enforce variable name conventions on booleans, like sticking an “is” in front or really old school “p” for “predicate” at the end.

@jym @foone

isEndian: True

@tuzgai @foone - My thinking is that they're trying to do `endian` as a [0, 1] enum and `isEndian` would look too ludicrous and show the the error of their ways. A guy can dream.

@foone should probably rename that…

`luscious_endian: True`

@foone need to write in a language whose operator overloading is so powerful that you can write "endian=>" or "endian=<" and have it work
@foone I can only hope this language stores "True" as a 1 in a storage type larger than 1 byte.
@sgf python, so... Yep!

@foone So, technically it is storing the endianness there and, as we all know, technically correct is the best kind of correct.

I'm intrigued. Is it deliberate?

@foone woulda been better if "true" was a string ;3