I have 4 characters (past and present) that all occupy the same “party role” for this reason. They each have their own back stories sure, but their decision-making process is essentially the same because it’s how I would solve that given problem. The same set of equations, just with different source data.
I hadn’t thought about over-exaggeeating a trait before to differentiate them, I may have to use that trick going forward.
Anyone else notice that a large flat rate box has the same limit and the post only counts a small flat rate box?
“The only difference between science and [messing] around is writing stuff down”
From memory I can only answer one of those: The way I understand it (and I could be wrong), your programs theoretically should only need modifications if they have a concurrency related bug. The global interlock is designed to take a sledgehammer at “fixing” a concurrency data race. If you have a bug that the GIL fixed, you’ll need to solve that data race using a different control structure once free threading is enabled.
I know it’s kind of a vague answer, but every program that supports true concurrency will do it slightly differently. Your average script with just a few libraries may not benefit, unless a library itself uses threads. Some libraries that use native compiled components may already be able to utilize the full power of you computer even on standard Python builds because threads spawned directly in the native code are less beholden to the GIL (depending on how often they’d need to communicate with native python code)
fail2ban isn’t a WAF?
The average damage on that is 45… Konsi OP
… What?
Or (insert MMO of choice)
Was not expecting a direct ref to Volo’s Guide. Love it.
For Certbot, I think it’s even further up the chain - OpenSSL. And if you’re installing it to Apache or Nginx, its probably just OpenSSL again.
My low level is a tad rusty from when I learned the C side in school, but if I recall the not operator resolves as a single Boolean (0 or 1 in true C), whereas compliment comes back as however many bits you put in - a not operation per bit.
In C, the not operator is ! and the compliment operator is ~
Only if you’re using a sign bit rather than two’s compliment (a sign bit allows for two representations of 0)
I’m no weather expert, but because you’ve got a regular pattern around the radar (the circle) that really shouldn’t appear in a normal weather condition, the beam may be getting grounded due to local conditions - see beam ducting.
The lil notch on the right is looks like it might be showing incomplete, conflicting, or out of bounds data. The site’s map legend may have a decoder for that pattern.
https://www.noaa.gov/jetstream/radar-beams
Or it could be the apocalypse, who am I to judge /j
Biblically accurate roadrunner wasn’t on the list of things I was expecting to see today
Looks like the video/image got over compressed or over enhanced. There’s probably not enough data in that file to reconstruct what happened here.
Linear or AI interpolation may make the image appear clearer, but it’s at the cost of creating new data that wasn’t already present.
Looks AI generated - wonky fingers on kitty’s right hand (left of image) and a partial cat face on their left index (right of image)
fedora themed music starts playing
Do be do be do, bah
Do be do be do, bah
“broken build” here likely refers to the phrase as defined by gamers to function as synonymous to “overpowered”.
As in, “the build is so broken you can’t/it is difficult to play against it”. This phraseology could be used by either an ally or an enemy, but it contextually changes connotation from positive for allies to negative for enemies.
Build is often used as a shorthand for a character’s combination of items, skills, and levels (as the various games define it).
YouTube’s a big place