caylus
Joined 11 years ago
Joined 11 years ago
Okay, great, we're getting somewhere. So you concede that the true number of human birth defects is on the order of 4-5 nines.
We know this because we've observed a huge sample size of human births. Meanwhile, the experiment you reference only observed a small set of planarian worm amputations. So we can't conclude there are even 4-5 nines of reliability there, let alone "100%".
Otherwise, we could simply observe a few hundred human births, observe no defects, and conclude that human births are also "100%" reliable.
In our original debate, we were both slightly wrong about the number of nines of reliability in human births. However, you are now infinitely wrong by claiming an infinite number of nines of reliability in planarian worm amputations. I don't know whether the actual number of nines is 5, or 10, or 20, but I can be certain that it's not infinity, because that would violate the laws of probability.
Then why not simply give the correct, still impressive, figure, as I suggested?
> the regeneration is always, 100% a head, if no change in the bioelectrical gradients
This is also a meaningless statement. It's correct 100% of the time, except when something goes wrong and it's not.
Can you quantify the likelihood of something going wrong with the "bioelectrical gradient"? I'm not familiar with this organism but I suspect it's several nines, but less than 7.
In general, probabilities less than a certain amount stop being meaningful, because it's more likely that the model used generate the probability fails to reflect reality. See https://www.lesswrong.com/posts/AJ9dX59QXokZb35fk/when-not-t...
This number is far too high. The rate of conjoined twins (violating "1 head") is about 1 in 50,000 [1], and the rate of "limb reduction defects" (violating "2 hands and 2 legs") is about 1 in 1,900 [2].
Those correspond to 99.998% and 99.94% respectively. 3-4 nines is still impressive for such a complex system, but let's not claim it's 7+ nines.
[1] https://www.chop.edu/conditions-diseases/conjoined-twins [2] https://www.cdc.gov/ncbddd/birthdefects/ul-limbreductiondefe...
In a flat monitor centered in front of your head, the distance between your eyes and different pixels on the screen varies depending on how close they are to the edge, thus distorting the sizes of the rendered sprites. Curving the edges reduces this effect (depending of course on the exact curvature and distance to the monitor).
I guess the key question for 3D is whether the rendering engine already attempts to compensate for this effect. It seems difficult for it to do so, since monitor sizes and distances vary so much, but I suppose that's what settings like field-of-view are for.
So we can divide the rental market into high-tax and low-tax properties. The landlords of high-tax properties must incorporate the tax into the rent. Meanwhile, the landlords of low-tax properties can set their rents just as high, since they compete in the same market, and pocket the tax difference.
In contrast, a flat property tax reduction would increase the profit margins of all landlords equally, and any one of them could start undercutting the others and be undercut in return, which over time in an efficient market will tend to lower prices back to a similar margin before the tax reduction.
I like the Go stdlib idiom for this: many functions have a version with a "Must" prefix that has the behavior of panicking rather than returning an error.
e.g. for regexp: https://pkg.go.dev/regexp#MustCompile
To be fair, failing to yield to oncoming traffic when turning left is an extremely common mistake for human drivers to make as well.
In fact, earlier in the video, the car correctly yielded to an oncoming car, the human driver overrode it, then complained that the oncoming car "cut him off"! https://youtu.be/yxX4tDkSc_g?t=494
For reference, this appears to be an example of that warning: https://github.com/MetaMask/metamask-extension/issues/11337
Transcript: "Signing this message can have dangerous side effects. Only sign messages from sites you fully trust with your entire account. This dangerous method will be removed in a future version."
Presumably part of the issue is that a legitimate "NFT mint" transaction might also carry the same warning.
It would be like using "a metal object that can harm people" as a working definition of an assault weapon. If the definition also includes ladders, cars, and push-pins, it's far too broad to be useful in any discussion.
If when my character levels up through gameplay they unlock a new ability, that would also seem to meet this absurdly overbroad definition of a "loot box".
Even if we added the requirement of real money purchase, offering some features of a game only as part of a paid expansion also has nothing to do with "loot boxes".
It's a similar case to cell phone providers: although there are hundreds in the U.S., all but four do not operate their own network, but rather resell the network of one of the big four.
It's an interesting question, though, how much this consolidation is due to regulation versus being a result of a natural monopoly, i.e. high barrier to entry for the type of business.
But if the loan defaults, the asset disappears, and if this happens enough the bank risks becoming insolvent and no longer being able to repay other liabilities like its deposits unless bailed out.
Maybe that's what you're alluding to - the Fed will always bail them out so deposits are never lost? That's probably true in practice, but a loan from the Fed can't in of itself restore solvency, since it's still both an asset and a liability. In the most extreme case, the bank would still go bankrupt, investors would lose their money, and depositors could also lose some of their money unless individually bailed out by the FDIC.
Back to the original discussion - the key question here is are people who hold cryptocurrency at Coinbase considered "investors" or "depositors", and are they protected by the FDIC? The latter is almost certainly no, and the former determines how much they can expect to get repaid if Coinbase goes bankrupt.
> When the user holds a key after tapping it, the tapping function is repeated by default, rather than activating the hold function. This allows keeping the ability to auto-repeat the tapping function of a dual-role key.
ref. https://github.com/qmk/qmk_firmware/blob/master/docs/tap_hol...
I use both space and backspace (in the caps lock position) as dual-function keys and find it very usable when I occasionally want to repeat-tap them.