![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://programming.dev/pictrs/image/170721ad-9010-470f-a4a4-ead95f51f13b.png)
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 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
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
I think I get it but explain nonetheless?
Let’s just hope that they won’t use it as a justification to put ads in your browser, or go the brave route.
Would be cool to be AI horde compatible and just ditch the GPU requirements entirely.
I don’t think everyone got a GPU that could run stable diffusion easily, even more for laptops
No one diss the gaming demon summoning circle! Sacrifice him!
But at least Firefox is just compatibility, and not phasing out v2
ROG spending all the points in style again
… And it’s working
Well it ses that bing is down too, and most independent search engines are a warper arround bing so…
Easier solution: Don’t use google
Inb4 normies force us to change well established terminology just to appease their fragile souls
Like git’s main and master
Fair enough lol
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.