![]() Been there, my new human bro, been there."Įdit: I wrote this before I saw the rest of the replys, and HOLY, there's a bunch of humans that don't understand why OP stopped playing. And it soured him on the whole experience. He wouldn't have wanted money, just a 'hey thanks for finding that for us'. So this hypothetical martian maybe would just smile, nod and say "Ah yes, the company was embarrassed, or didn't want to risk liability, or didn't want to risk their reputation being compromised. In fact, it's quite possible, that this is a necessary prerequisite, side effect, or consequence of conscious intelligence. That we're illogical and inconsistent and jealous and petty and insecure, but also humble and funny and empathetic and creative.īut.we have no evidence that this would be unique about humans whether sentient intelligence is common throughout the universe or rare. Our science fiction is filled with this fairly human-chauvinistic worldview where even in a hypothetical future where we are rubbing shoulders with many different alien species, many of them technologically superior to ours, some of them still admire or begrudgingly respect us for our ingenuity, spirit, some je ne sais quoi. I was disappointed and stopped playing.īut here's another layer, though. They did not reply and just silently fixed the bug, right after my email. I wrote up exactly this in a short email to the company that made the Yahtzee game. The crucial point being to use floor() or ceil() instead of round(), to only round towards one direction. ![]() Add 1, and you have the dice value.īut the ranges for dice values 1 and 6, are only 0 to 0.5 and 4.5-5 respectively, so ranges that are only half the size. So any value between, say, 1.5 and 2.5 (exclusive at one end) rounds to 2, 2.5-3.5 rounds to 3, and so on. The problem is that round() rounds to the nearest integer. Almost certainly, they had a random number generator giving a number in a uniform range, let's say from 0 to 1, and did something like the following to get a dice value from 1 to 6: Seeing the result, the problem was pretty clear, without even knowing the source code. (And because I was studying for my statistics minor in university at the time). I even did a chi-squared hypothesis test, because I was crazy. Turns out I was right, the distribution was not uniform: 2-5 were fine, but it seemed that it was twice as hard to get a 1 or a 6 compared to any other value. I felt more and more that dice values of specifically 1 and 6 were harder to come by than other values, so one day I sat down for a few minutes and logged the value of 100 or so dice throws. For me it was something to fidget with (there was no money involved or anything, just a personal high score), so I played it a lot. It was one of the most popular games on there. I don’t think it’ll be final solution, but its a direct translation from how i was handling it in react-router v2.Around 15 years ago, when casual little games on Facebook were still a thing (actually when Facebook itself was still a thing), I used to play Yahtzee on the site while watching TV shows or whatever. ((need) => needs.push(dispatch(need(match.params))))Īwait getData(store.dispatch, ctx.request) Note: the getMatch function isn’t very sophisticated - i expect i could be improved somewhat to match multiple paths or nested paths etc // middleware/set-router-context.js ![]() feel free to come up with a better name!) then i use the store to dispatch the method. If the matching path has a component with a static method of ‘needs’ (as in needs data. If so, this is how i handle it i have created a middleware on the server to match the req.url against the routes. If i read your question right, you have components which contain a static method for fetching data, probably redux actions?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |