Generally yes vasectomy is safer. But if they’re planning to give birth via c-section for whatever reason for example, then in practical terms there’s basically no additional risk. Plus neither method is totally effective. So if you can both get fixed you have much better chances of not getting pregnant accidentally.
We moved hospitals for the birth of our twins to find one that was willing to tie her tubes when they took the twins out. She ended up having to have a hysterectomy for other reasons later but them being willing to tie her tubes during the c-section was a big part of our decision on doctors to see.
My mom had a hell of a time getting her tubes tied after my brother was born. She had to argue with the doctor for a while to eventually get it done. Gave her the old “What if you change your mind later?” line in like 5 different variations. The one that really angered me though when she told me the story was “What if something happens to one of your children?” Like you were just replacing a busted TV or something.
#include <stdio.h>
int main() {
Long long x = 0x7165498511230;
while (x) putchar(32 + ((0xC894A7875116601 >> ((x >>= 4) & 15) * 7) & 0x7F));
return 0;
}
Might be wrong on a few things here as I haven’t done C++ in a while, but my understanding is this. I’m sure you can guess that this is just a very cheekily written while loop to print the characters of “Hello, World!” but how does it work? So first off, all ASCII characters have an integer value. That 32 there is the value for the space character. So depending on what ((0xC894A7875116601 >> ((x >>= 4) & 15) * 7) & 0x7F)) evaluates down into you’ll get different characters. The value for “H” for example is 72 so that first iteration we know that term somehow evaluated to the number 40 as 72 - 32 = 40.
So how do we get there? That big number, 0xC894A7875116601 is getting shifted right some number of bits. Let’s start evaluating the parenthesis. (X >>= 4) means set x to be itself after bit shifting it right by 4 bits then whatever that number is we bitwise AND it with 15 or 1111 in binary. This essentially just means each iteration we discard the rightmost digit of 0x7165498511230, then pull out the new right most digit. So the first iteration the ((x >>= 4) & 15) term will evaluate to 3, then 2, then 1, then 1, etc until we run out of digits and the loop ends since effectively we’re just looking for x to be 0.
Next we take that number and multiply it by 7. Simple enough, now for that first iteration we have 21. So we shift that 0xC894A7875116601 right 21 bits, then bitwise AND that against 0x7F or 0111 1111 in binary. Just like the last time this means we’re just pulling out the last 7 bits of whatever that ends up being. Meaning our final value for that expression is gonna be some number between 0 and 127 that is finally added to 32 to tell us our character to print.
There are only 10 unique characters in “Hello, World!” So they just assigned each one a digit 0-9, making 0x7165498511230 essentially “0xdlroW ,olleH!” The first assignment happens before the first read, and the loop has a final iteration with x = 0 before it terminates. Which is how the “!” gets from one end to the other. So they took the decimal values for all those ASCII characters, subtracted 32 then smushed them all together in 7 bit chunks to make 0xC894A7875116601 the space is kinda hidden in the encoding since it was assigned 9 putting it right at the end which with the expression being 32 + stuff makes it 0 and there’s an infinitely assumed parade of 0s to the left of the C.
I guess it’s a special kind of character called a ligature. They apparently are characters for combined operators. So in this case it seems to just be >>= all as one character?
Fuck the Big Light™
For real. I get migraines and one or my big triggers is lights being too bright. With good old Sol being the worst offender. Luckily everyone else in my house is some flavor of autistic/ADHD so pretty much everyone agrees.
Fuck the Big Light™
Yeah that seems like a bit of a stretch. That meme read to me like “Oh, you’re having problems with the DRM? I don’t have that problem,” not “Hey guys, here’s the GOG installer for X game.”
Otherwise, why would the other people in the group chat not like the vibe?
Not really. Using % of forecast area as % chance of rain inherently gives equal weight to your position being anywhere within that area. Even if you limit the forecast area to the 5m or whatever it is radius that smartphone GPS is typically accurate to which a weather app could theoretically do, simply using % of the forecast area covered as % chance of rain inherently gives equal probability of you being literally anywhere within that 5m radius. It would obviously still be more accurate, but those numbers wouldn’t be the same thing.