Countries with sane laws include a tolerance limit to take into account flaws in speedometers and radars. Here in Brazil, the tolerance is 10%, so tickets clearly state "driving at speed 10% above limit".
That is not sane, it is dumb. With such a system, you have signs that say "100" but the actual speed limit is "110" and everyone knows the actual speed limit is "110" but they all have to do mental math to reach that conclusion. Just make the sign say the real speed limit instead of lying to you. It's like Spinal Tap wrote your laws.
It’s not dumb, it’s accounting for real world variance in car speedometer accuracy and possible inaccuracies in the measurement process, just because your car is telling you you went 98 or the speed camera is telling you you went 101 doesn’t mean that was the actual speed of your car at the moment.
Speed limits are limits, not targets. That's why they're called speed *limits*. You account for variance in the speedometer and the reading device by staying under the limit, not treating it as a target.
I hope this does not come across as antagonistic but isn’t this then another form of mental math again? "I’m actually not allowed to drive the number on the sign but I’m also not allowed to drive a speed within the margin of error so I could be falsely accused of speeding."
The other way around seems more clear in a legal sense to me because we want to prove with as little doubt as possible that the person actually went above the speed limit. Innocent until proven guilty and all that. So we accept people speeding a little to not falsely convict someone.
So your speedo reads 100 km/h in a 100km/h hour zone. The intention is that you just treat that as a sign that you're at the limit and don't go faster.
Yes, you _could_ do some mental math and figure out that your speedometer is probably calibrated with some buffer room on the side of overreporting your speed, so you're probably actually doing 96km/h and you know you probably won't get dinged if you're dong 105km/h so you "know" you can probably do 110km/h per your speedometer when the sign is 100km/h.
Or you could just not. And that's the intention. The buffers are in there to give people space for mistakes, not as something to rely on to eke 10% more speed out of. And if you start to rely on that buffer and get caught on it, that's on you.
As a driver, I control my speed for a variety of factors, but I assume no responsibility for the variance in the speed checking device. That’s on the people deploying them to ensure they’ve done their job (and is part of the reason tickets aren’t issued for 1kph/1mph over in most jurisdictions).
I understand where you’re coming from, but it’s perfectly sane if your legal system recognizes and accepts that speed detection methodologies have a defined margin of error; every ticket issued for speeding within that MoE would likely be (correctly) rejected by a court if challenged.
The buffer means, among other things, that you don’t have to bog down your traffic courts with thousands of cases that will be immediately thrown out.
So the sign says "100", the police read your speed at "112" but the device has a 5% MoE and in this case your actual speed was 107. Seems like you have exactly the same problem because the laws state the actual speed limit was "110" which you are under, despite being over the posted limit and the police reading you as over both the real and posted limits.
I don't know enough of the 8086 so I don't know if this works the same, but on the Z80 (which means it was probably true for the 8080 too), XOR A would also clear pretty much all bits on the flag register, meaning the flags would be in a known state before doing something that could affect them.
The last thing we need is more enshitification on this space.
I just migrated my selfhosted email server to Hetzner and I don't want them turning into monstrosity like AWS or Azure, with theit miriad of ways to nickel and dime the customers.
I run desktop Linux. It's pretty hard to switch a billion desktops to Linux even if you do it one at a time. Not to mention a ton of problems with compatibility and corporate and government IT
That is assuming the objects will be at the same place relative to us, which is not true. Like reaching Andromeda. Voyager I will reach oyr neighbouring galaxy in roughly 4.5 billion years, not 45, that's because Androneda is moving in our direction. Reaching Proxima Centaury would take longer than your estimation because of it's orbit around Alpha Centauri A/B.
Estimating time-to-arrival when your destination is also moving at ludicrous speeds is incredibly difficult.
