![](/static/66c60d9f/assets/icons/icon-96x96.png)
![](https://programming.dev/pictrs/image/170721ad-9010-470f-a4a4-ead95f51f13b.png)
To whoever does that, I hope that there is a special place in hell where they for 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
To whoever does that, I hope that there is a special place in hell where they for 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
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.
See edit
See edit
This one isn’t even an XKCD. This is just a shitpost
My attempt to explain was squashed by this comment
It’s the second time I see it on a programmer humor community. I get you want to advertise, but we already told you that this isn’t the place for that
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
Virgin toddler squasher Vs chad adult compressor
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
Or as would Dearrow put it: “Explaining the Effects and Treatment of M. Tuberculosis”
Or as I would put it: “Big space cum monster is a threat to earth”
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?
I don’t see how making noise is good. I live in a street that doesn’t get much traffic, but even one car is loud enough to be bothering.
I don’t want to pause my music and conversations just because someone decided that vroom vroom sounds were more important than me hearing literally anything else.
Even more that noise pollution is definitely a thing, and affect both mental health and physical one.
I’ve started to become 2) for some stupid reason.
I use btrfs snapshots to backup my system, and it has the side cost of needing a bit extra space. This is absolutely fine.
What is not fine however is free desktop/Nvidia flatpaks update. I get 10gb every week, and it keeps filling my disk with this stupid crap.
Not only that I am both a rust programmer and blender artist, and it’s the trinity of non deduped disk space filler
We got the dank Linux syndrome.
Instead of brain there’s a tux doing shitposts.
It’s terminal
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.