And then JSON doesn’t restrict numbers to any range or precision; and at least when I deal with JSON values, I feel the need to represent them as a BigDecimal or similar arbitrary precision type to ensure I am not losing information.
And then JSON doesn’t restrict numbers to any range or precision; and at least when I deal with JSON values, I feel the need to represent them as a BigDecimal or similar arbitrary precision type to ensure I am not losing information.
That’s because the nearest representable float to 0.99999999999999 is 1.0 - not because Python is handling rationals correctly.
This is a float imprecision issue that just happens to work out in this case.
It’s worth wondering why, if Python is OK with “/“ producing a result of a different type than its arguments, don’t they implement a ratio type. e.g. https://www.cs.cmu.edu/Groups/AI/html/cltl/clm/node18.html#SECTION00612000000000000000
How would you implement this in code?
JavaScript is truly a bizarre language - we don’t need to go as far as arbitrary-precision decimal, it does not even feature integers.
I have to wonder why it ever makes the cut as a backend language.
You have to explicitly check if the return value is an error and propagate it. You write the same boilerplate
if (err) return err
over and over again, which just litters your code.
That’s only true in crappy languages that have no concept of async workflows, monads, effects systems, etc.
Sad to see that an intentionally weak/limited language like Go is now the counterargument for good modeling of errors.
If you think of low frequencies as “red” and high frequencies as “blue”, corresponding to the range of the visible light spectrum, then pink noise has more “red” and less “blue”; white noise has equal amounts of all frequencies, etc.
Performance is the major flaw with microkernels that have prevented the half-dozen or more serious attempts at this to succeed.
Incurring context switching for low-level operations is just too slow.
An alternative might be a safe/provable language for kernel and drivers where the compiler can guarantee properties of kernel modules instead of requiring hardware guarantees, and it ends up in one address space/protection boundary. But then the compiler (and its output) becomes a trusted component.
Yes, it is a huge pain, especially if you want to have round-trip interoperability with humans using markup. Wikipedia had a major challenge with this when they decided to add a rich text editor alongside wiki markup.
Surge suppressors do not drop extra voltage to ground. They selectively short out surges between whatever two conductors have a high potential between them.
No ground conductor means there cannot be a high potential between it and anything else!
What? No. Electricity takes all conductive paths through a circuit simultaneously, with a current in inverse proportion to the path resistance. Ground means nothing unless it somehow makes up a part of the circuit - it is neither a “sink” nor “zero” for electricity. It’s just dirt.
Guys, he made the joke!
If your company is using story points to “measure” developers, they are completely misusing that concept, and it probably results in a low-teamwork environment (as you describe).
The purpose of story points is so a team can say “we’re not taking more than X work for the next two weeks. Make sure it’s the important stuff.” It is a way to communicate a limit to force prioritization by the product owner.
And, in fact, data shows that point estimation so poorly converges on reality that teams may as well assign everything a “1”. The key technique is to try to make stories the same size, and to reduce variability by having the team swarm/mob to unblock stuck work.
Who creates these tasks? They need to close the year old items, reevaluate the work and break it down into sub-5-day chunks. If there are so many unknowns that it’s impossible to do that, the team needs to brainstorm how to resolve them.
fyi the NeXT OS is called NeXTSTEP.
Fun fact: a US nickel weighs 5.000g, and 5 US quarters weigh 1.0000oz
FYI, banks do run exactly this type of analysis inside their own system to get around not being able to share your account activity.
It was a PowerPC OS way before it was ever an (Intel x86) PC OS. First on dedicated hardware, later adding support for PowerPC Macs.
along these lines, you should also know about the condensate drain from your air conditioner – since water drips out of it all summer, it has a tendency to grow some algae or mold, and if it plugs up your air conditioner may flood and ruin your ceiling/walls/floor.
it’s worth paying that AC guy to come by every couple of years even if you’re not on their service plan.
for what it’s worth, coolant is not consumed by an air conditioner – the same initial charge can last 20+ years. Low coolant either means a leak, which the technician should have investigated and fixed or ruled out, or improper initial installation.
Could be a crypto key, or a randomly distributed 64-bit database row ID, or a memory offset in a stack dump of a 64 bit program