my most unfavourite thing is when javascript guys make a data structure that uses a string to define a type

because i have to then write code that unmarshals all of that shit into generic forms, and then re-encode it to an actual typed structure

it takes a full screen vertical of code just to do one of these types usually

is there some reason you want to use an array for something?

please, use objects and let me define the type by the fucking object element key name

this is so much more work doing it this way

i remember first bumping into this with nostr filters

like, is there some particularl reason you couldn't have defined that a-zA-Z list of "#" fields as an actual array, which is what they are?

oh no, we hate nulls, nuls are awful, we prefer to leave them out of the json because reasons

fuck you, and the horse you rode in on

you may not be aware of this, but there is a whole rainbow of bugs that exist because of this kind of idiotic dynamic type definitions, and an incredible amount of processing overhead required to decipher the intent of the programmer

this is why some of us hate OOP languages

because you don't seem to understand that making a computer figure out human intent is absurd