As if I had a choice. Most of the time I'm only on the receiving end, not the sending end. I can't just magically use something else when that something else doesn't exist.
Heck, even when I'm on the sending end, I'd use JSON. Just not bullshit ones. It's not complicated to only have static types, or having discriminant fields
Sadly it doesn't fix the bad documentation problem. I often don't care that a field is special and either give a string or number. This is fine.
What is not fine, and which should sentence you to eternal punishment, is to not clearly document it.
Don't you love when you publish a crate, have tested it on thousands of returned objects, only for the first issue be "field is sometimes null/other type?". You really start questioning everything about the API, and sometimes you'd rather parse it as serde::Value and call it a day.
To whoever does that, I hope that there is a special place in hell where they force you to do type safe API bindings for a JSON API, and every time you use the wrong type for a value, they cave your skull in.
I would do that... If CI wouldn't be set to -D warnings
Who even does that? Oh wait, it was me.
Joke aside, it does help to keep the code clean, even more for open source projects where multiple separate people may all have their own codding style, and it helps make it easier to organise.
But I do agree that it can be really, really annoying.
Nah. They are supposed to not care about stuff and just roll with it without any regrets.
It's just like the wojak crying with the mask on, but not crying behind it.
There's plenty of cases of memes where the giga chad is just plainly wrong, but they just don't care. But it's not supposed to be in a troll way. The giga chad applies what it believes in.
If you want a troll, there's troll face, who speak with the confidence of a giga chad, but know he is bullshiting
This isn't even an issue of middle ware sometimes. It's just... Knowing the DB. And I rather not spend time learning when you can just make docs