Don’t worry. People actually throwing things in the trash instead of anywhere else is uncommon

Good and bad use-cases for floats

Floats can be used everywhere where it doesn’t matter that you can’t store a 100% accurate base ten representations. For example positions and speeds in 3D games and animations, “analog” values like temperatures, speed of a vehicle, geo positions with longitude and latitude, a persons weight or heart pressure. In fact if you develop games there is no way around 32 bit floats because GPUs are f32 number crunching beasts. Modern 3D games wouldn’t be possible without all those fast f32 calculations.

You shouldn’t use binary floats if you need or expect accurate base ten calculations (addition, subtraction, multiplication, - note that divisions also introduce errors quickly in decimal types) and for dimensions that have a smallest unit that can’t be broken down, for example like money. If you need to handle money just store the amount of cents as integers and only divide by 100 in your display function.

This is exactly my point. Don’t use floats when you need to get accurate stuff, but use it when you need a “feel” for it

if true

Oh I didn’t mean editing the first icon. It could be remade from scratch.

I’ll see if I can try doing it tonight

(Outsider here)

Why not the same as 1, but with a blinking Lemmy logo like (2)?

?

Change the ❌ for a ♻️. It almost looks like a "what Paris did wrong " section

Mint is my favourite distro. Is everything I want from my computer.

… Except the Nvidia support. I need the actual proprietary driver for cuda and it’s not the easiest of rides.

(I switched to Nobara for better support and now the drivers memory leak. I need the courage to distrohop again)

c:/

I’d actually recommend consent-o-matic instead of IDCAC. It actually selects the minimum concent for you instead of just hiding it.

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

This was a really funny scroll up. Thanks op

He has found the precious… Braincell

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.