I think they are referring to crates vs binaries vs cargo binaries.

Crates are your libraries, not meant to be standalone, binaries are your .exe, cargo binaries are meant to be compiled by cargo on your machine and run through cargo, ex: cargo sqlx

They might also refer test binaries and example binaries which are two executables that only compile the tesrs and the examples to make sure they work, but apart from that idk

I love this game. On multi screen it gets so big

Don’t put a fast charger for overnight charge. It degrades the battery. I got my charger hooked up to my server’s usb port and it’s able to charge a 10000mha battery overnight at nearly 100% from low percents.

I would have gone silent mode but I was jamming to some music so I heard it

Is there an original without the music?

I think the meme refers to the joke that “all guys just want a big tiddy goth girlfriend” meme.

The bottom text is just a joke to divert from the obvious meme

Half joking. Lifetimes can be hard but once you understand the concept it’s quite easy.

The second joke is about you never learn Rust. You’re always on the learning rollercoaster. Always one step away but each time it makes you rethink the whole language.

Don’t get me wrong, I’m a rust main. But does issues does exist

Rewrite it in rust. Now get a lifetime of problems

Dog pile?

Good joke, ruined by the art

tea_bag.unwrap()

I get 100m up front, right?

Right?

Delete container, rebuild container. Sometimes it’s just useful to clean up all the mess of cache files

You’re lost. This ain’t the place to post that.

Also “candy box” is a waffle menu

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