If he mentions it, one has to assume that he knows enough about it to lie.

The ultimate red flag. They probably lie about paying you, too.

Speedy recovery, and all the best!

OK, I have not played it for AGES. Nice to see something like that fixed, as it was a bit system-inherent.

All kinds of weird things. There is a video explaining the details, and you’ve got to be far, far out.

Where the heck did I “shit on people using floats”?

Like Minecraft has, too. Just go on a long, long walk in one direction.

Yep. And in accounting this is done with integers. In my field (not accounting), calculations are done either in integer or in fixed-point arithmetic - which is basically the same in the end. Other fields work with floats. This variety exists because every field has its own needs and preferences. Forcing “One size fits all” solutions was never a good idea, especially when certain areas have well-defined requirements and standards.

As you said, better use integers. And that’s exactly what is done at this point.

I did clarify my reasons. That you obviously didn’t read.

I fail to see a difference there

That I noticed some posts ago. The issue has not changed since then.

Yes, you are not wrong here.

What I regularly have to deal with is about as bad. Big project, and every upgrade replaces one key element. They have never heard of backwards compatibility. If they don’t like a subset in their system, they replace it. Complete with different API calls, structures, and calling conventions. And they may document parts of it three versions later. If at all. Some documentation is basic Doxygen - just list the function parameters, and that’s it. I’ve seen cases where the documentation of the rather critical parameter “flags” was just the word “flags”. I’ve seen cases where the return value was documented only as “status”. Not even with a notion whether 0==success and 0!=failure or vice versa.

And no, it is not a closed application. They have an “extension” folder for user-supplied extensions. The problem: If it is not a core extension that has been updated with the main project, the first thing after an upgrade is finding out where your formerly working extension critical to your project now fails, because they just happened to think that the call interface for the boogaloo object need a complete overhaul. Maybe it needed an overhaul, but then at least keep the older interface alive for at least a few versions after documenting the new interface and marking the old one as deprecated.

The issue is different. Imagine you have ten dollars that you have to spread over three accounts. So this would be 3.33 for each, absolute correctly rounded down. And still, a cent is missing in the sum. At this point, it is way easier to work with integers to spread leftovers - or curb overshots.

Nope. With about a hundred thousand factored items, things easily run off the rails. I’ve seen it. Just count cents, and see that rounding errors are kept in close, deterministic confines.

I stopped using floats 30 years ago when I learned what rounding errors can do if you only deal with big enough numbers of items to tally. My employer turned around 25M a year, and it had to add up to the cent for the audits.

The Gleichschaltung has started.

“Only material that is clearly child sexual abuse will be searched”

Searched in what? All open and private discussions? That is the whole f-ing point!

Stick with NFS, and use e.g. rsync for backup. Or subversion, if you want to be super-safe.

Other sites should join to show the citizens how a blacked-out internet looks like.

Kardashian today vs. Kardashian in 10, 20 years.