Half of it. This gives you the running count. You need to also keep track of “number of decks in shoe” -“number of cards dealt since last shuffle”/52 to tell you how many decks are left in the shoe, then divide the running count by the number of decks left to give you a true count.
True count higher than 1? Start increasing your bet accordingly.
I think the saddest part of the whole LTT debacle is realizing how many people confuse Linus Torvalds, the creator and maintainer of the Linux kernel, with some click-bait creating YouTuber who can barely operate a Linux desktop.
Except strict equality, that’s a JavaScript only problem. Imagine thinking “0” should be falsy in comparison due to string literal evaluation, but truthy with logical not applied based on non-empty string. Thus !“0”==“0” is true. They couldn’t just throw away == and start over nooooo let’s add === . Utter madness
Browser compatibility. Design flaws can’t easily be fixed like how other languages can just switch to a new major version and introduce breaking changes. ES must keep backwards compatibility so has had to do more additive changes than replacing behavior altogether so that older web pages pages don’t break.
Strict vs loose equality has gotten me so many times, but I can sort of see why they did it. The problem you mention with integers 0 & 1 is a major annoyance though. Like it is fairly common to check whether a variable is populated by using if (variable) {} - if the variable happens to be an integer, and that integer happens to be 0, loose quality will reflect that as false.
But on the other side, there have been plenty of occasions where I’m expecting a boolean to come from somewhere and instead the data is passed as a text string. “true” == true but “true” !== true
Lua does intrinsic evaluation of strings that i’d argue is not nearly as crazy. I get the value of it since half of interpreted languages it just churning through strings. But I also don’t recommend any large codebase ever use JS’s == or string coercion because it can go against expectations. This graph argues in JS’s favor but comparison is a little more crazy algassert.com/…/Better-JS-Equality-Table.html
Half-pull the lever so that the points get stuck midway between the two tracks. That should derail the trolley. Someone could conceivably still get hurt, but it improves everyone’s chances.
(What? You mean it isn’t a literal trolley that has to obey the laws of physics? Damn.)
Except that somewhere down that chain someone is almost certainly going to choose to kill people, so by passing the trolley on down to them you're responsible for killing a lot more than if you ended it right now.
And since every rational person down the line is going to think that, they'll all be itching to pull the "kill" lever first chance they get. So you know that you need to pull the kill lever immediately to minimize the number of deaths.
Only the person pulling the lever is responsible for his/her action though. There is a difference between passively passing on and actively murder someone
If I hand a machete to Jason Voorhees I think I'm at least partly responsible for the people he hits with it. I know what he's going to do with that thing.
I guess it comes down to the weight you give the word "possible" in your sentence. If possible means extremely likely (and there are logical reasons to believe so) then taking responsibility makes sense.
Except you're not passing a machete to Jason Voorhees. That would be "double it and pass it to the next person who you know is going to pull the lever."
You're passing a machete to the next person in line. You don't know who that is. They may or may not pass the machete down the line. Considering I would not expect a person chosen at random to kill someone when handed a machete, it seems unethical for me to kill someone with a machete just to prevent handing it to someone else.
Or it keeps doubling even well after its surpassed the human population, and we all have to keep hitting "pass" in turns forever, and if even a single person gives up then boom.
That’s only if he’s next in line though. If you pass a machete to someone who might one day eventually pass it onto him, is that as bad? I suppose at some point there’s an ethical cutoff lol
The farther away he is the worse it is because the more people he gets to kill. If for some reason I absolutely had to pass the machete down the line then the best case is for the very next person I hand it to to be Jason. But even better if it's me.
In this case it isn’t even a guarantee that anyone has to die as the problem is presented, the tram can just continue to be passed along. The default setting for the lever is “go to next” so to not pull the lever is easier both physically and morally.
The individual that pulls the lever is the same individual that would take action to harm others for no benefit, and even in real life I can’t morally take responsibility for a person who runs over a child by purpose after I let his/her car merge in front of me just before a school crossing
I guess then the issue would be: do you ever find out the result of your actions? If no, then I guess it’s sort of a “glass half empty/full” kind of thing, because you could just pass it on and assume the best and just go live your life quite happily.
Although if you did find out the result, imagine being first, pulling the lever and then finding out nobody else would have.
If it’s infinite (up to the current human population), we’re all tied up on the tracks. Unless we’re leaving out the exact number of people that would bring it to approximately the full population, I guess.
As long as I’m not on the tracks, I’ll take the hit and kill one instead of risking a potential genocide.
I don’t have to be a soldier on anyone’s ethical recursion war, so since the default position is set to kill 1 person, that gets done by the problem itself and the whole thing is solved without me having to do anything.
As a further bonus, now the lever people on the next branches are free to get out of the levels and go release the other prisoners.
Seconding that, made the switch and nothing broke since(almost 2 months now, ^o^) . Can’t say that for windows tho, where not only auto updates meant I had to wait half an hour to use my PC half of the time or disable them and not be up to date with security, but the OS itself was riddled with problems, sometimes just opening Firefox with a few tabs (like 4 or so) would bsod (and I have 16 gigs of ddr4 ram, so it wasn’t a ram problem) not to mention now that I’m on Mint everything is faster, I didn’t have to pay a license key and I know my OS isn’t trying to fight me for my data.
Thanks for your addition! It is working fine for me, but I may have changed the config a bit from the default, don’t remember everything. I have default tiling now and that works really well.
One of the things that is a must for me is 1 panel that shows the windows and apps per monitor. I can’t work any other way, I’m not looking to drastically change my workflow more so than Linux alone already is. My quick Google search said that it wasn’t possible on Gnome 44 and I gave up.
That said, KDE is laggy and unresponsive. It’s also fairly unusable. Everything else besides those 2 is like going back 20 years to desktop environments of the olden days. I just want something modern that works with my workflow.
programmer_humor
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.