I got nothing against other types. Just numbers/misleading types.

Although, enum variants shall have a label field for identification if they aren’t automatically inferable.

This is understandable in that use case. But it’s not everyday that you deal with values in the range of overflows. So I mostly assumed this is fine in that use case.

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

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

The schema is this SQL statement

If a item can have different type, those label fields are actually quite useful. So I don’t see the problem

You guys have docs?

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.

Sincerely, a frustrated Rust dev

See edit

See edit

This one isn’t even an XKCD. This is just a shitpost

Edit: I meant that it doesn’t have the XKCD vibe. Not that it isn’t an XKCD.

Usually, XKCDs are extremely nerdy and touch scientific subjects. But here, the joke is something I’d see in the local meme community.

My attempt to explain was squashed by this comment

I do push often as I’m often switching between two devices. And I do make draft PR so I got an easy git diff that I can live reference with

I often do the same for my memes. I like them high quality

NGL I 'm a bit like that. I often do “work” commits so that my working tree is a bit more clean/I can go from working state to working state easily.

But before a PR, I always squash it, and most times it’s just a single commit

Also, looking at the road, it doesn’t seems to be that bad. It ain’t central France bad

It’s an option!? I get severely motion sick in cars and I’d love those easier roads

I think I get it but explain nonetheless?

Could you explain your choices better? Like what makes the top tier so good, and why the bottom tier is so bad?