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

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

The schema is this SQL statement

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.

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

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

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

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

My attempt to explain was squashed by this comment

*bad Devs

Always look on the official repository. Not just to see if it exists, but also to make sure it isn't a fake/malicious one

I won't lie, but content like this is what I love on programmerhumor.

Also just use the (inferior) open source version of GUMBIES called GRUMBOSS. It's way better!

If only they made the hole square....

Yeah fuck this.

... What's a translation layer?

That's a win, but it would need to be enforced... Which is harder to do

Well it ses that bing is down too, and most independent search engines are a warper arround bing so...

?

From someone in computer networking classes: "I don't use GitHub. This is too complicated" Like bruh. The instructions are right there in the readme.

There's also the time where we were asked to read temperature from a sensor, and everyone went straight to chatgpt. Meanwhile, first search result, full repo with full noob instructions.

Well if you get asked for sudo, then that's a risk.

Same, and I'm trying to fight against it. I've noticed that when coming home I am not just procrastinating, but actually exhausted. Idk if it's due to concentrating all day, or something with me, but I do know that I am tired.

I've started to actually embrace it, and for the time until I get dinner, I just rest. Might sleep even. There's no point in fighting, as I aren't in the mental space to do things. Then after dinner I'm back to do stuff, maybe even later in the night as I am more rested from my nap.

Although another take on it is that things are lot more enticed to do things when you can't/don't have them.

I am not a doctor, nor claim what I do is healthy, but that's just my experience. If anyone got tips I'm listening

Ah yes. That's what the kids call "sqlx" right?

NGL, if it has real time code completion and compile time SQL checks, this is fine.

But at least Firefox is just compatibility, and not phasing out v2

Inb4 normies force us to change well established terminology just to appease their fragile souls

Like git's main and master

Easier solution: Don't use google

I'm way to used to doing nano file.txt that I always forget about touch.

Although most times, if I create a file, it's to put something in it

But they smell nice!

Not joking even. My steam deck still have that sweet new shiny thing smell.

As a non native speaker, this messed me up for years

I always heard about "being up" for something, so I logically assumed that being down meant the inverse. Even more that "feeling down" usually means not being able to do things.

Not a go dev. Is it really preventing compilation or is it just some hardened linting rules? Most languages can prevent compile on those errors if tweaked, but that seems bad if it's not a warning

?

shit myself

You should be able to post on Mastodon while on lemmy

Let's just hope that they won't use it as a justification to put ads in your browser, or go the brave route.

No one diss the gaming demon summoning circle! Sacrifice him!

You can't get dumber than that

(I want to see them get dumber)

[insert obvious skibidi joke here]

Look at the user counts. This is exactly what it is. People like it enough to download it.

As for why mixing them up... Well... That's just classic store search things. "You may like this too" or "You may be in the wrong place to browse themes"

There's Listenbrainz, but it's more artist based.