I'm not an authority on this, but here's is my understanding - I'd appreciate if someone could correct my mistakes.
The baseline of 0.0 represents the average of all years. Anything above / below the baseline is a (standard) deviation from the average. The blue lines are the individual years since 1991 [1] while the red line is the year 2026.
If a line is above the baseline, then the sea-surface temperature was hotter on that day than average. If below, it was cooler than average.
The year 2026 is an outlier, dwarfing all the others starting around June / July. The Nino 3.4 sea-surface temperature is significantly hotter than any previous year during that time. New record, I guess?
[1]: I'm confused about the two date ranges given: 1982-2026 and 1991-2020. I'm assuming this graph is based on measurements from 1982-2026 to calculate the average, but the lines shown are only from 1991-2020, for some statistical reason I don't understand.
But think of those poor megacorps! How will they ever turn a profit without their precious algorithms? Invading every user‘s privacy is only morally right! What else could they, or governments, possibly do? Make line not go up? I shudder to think!
> It is saying that each of them can use the others body as they like, without regard for the other
This is your own interpretation and it shows your bias. The bible (and I assume other religious texts) is easy to misinterpret due to bias. It's not written like a technical documentation where the tiniest details are specified; thus giving plenty opportunities to subject a text to arbitrary meaning.
This was a problem even in biblical times. 2 Peter 3:16
> as also in all of his letters, speaking in them of these things. In those, there are some things that are hard to understand, which the ignorant and unsettled twist, as they also do to the other Scriptures, to their own destruction.
The solution is study. Not superficially reading and guesstimating, but to study the text itself, the surrounding verses, the context. Who wrote it? Who's the audience? What, more broadly, are they trying to say? Crosschecking with other verses in bible. Things like that (See Proverbs 2:1-5, Psalm 1:2, Joshua 1:8, Psalm 119:97, 1. Timothy 4:15)
Coming back to the text in question (1. Corinthians 7:4). The surrounding verses provide context on what this is about:
> To the unmarried and the widows I say that it is good for them to remain single, as I am. But if they cannot exercise self-control, they should marry. For it is better to marry than to burn with passion.
> Let the husband give to his wife her due, and let the wife also do likewise to her husband.
> Do not deprive each other except by mutual consent for an appointed time [...].
Put simply: "marry and enjoy sex." That's basically what the apostle Paul is trying to say here. But of course, that alone doesn't debunk your interpretation.
Paul also wrote Ephesians 5:28-33
> In the same way husbands should love their wives as their own bodies. A man who loves his wife loves himself, for no man ever hated his own body, but he feeds and cherishes it [...] Each one of you must love his wife as he does himself; on the other hand, the wife should have deep respect for her husband.
Also vers 25:
> Husbands, continue loving your wives, just as the Christ also loved the congregation and gave himself up for it.
There are further verses, but this comment is getting too long.
> 'Panzer', of course, is a famous Nazi tank model
Panzer is German for tank, or armor. It‘s not referring to any model specifically, I don’t think, but I‘m not a historian.
Panzerschreck (spelled correctly) is something like „tank scare“.
But indeed, that GitHub page gives off the wrong vibes. Using this project will be tough, at least in Germany and Austria, lest you want to be suspected of Wiederbetätigung.
What you‘re looking for is called a low-profile TKL (tenkeyless aka. no numpad) keyboard. You might also like a 65%, which removes even more keys but still retains the arrow keys.
I think the idea is to avoid problems with functions or APIs that have side effects. You want to make sure you perform the task only once. Or you want to make sure you’re not burning money on some commercial API through redundant calls. It‘s not necessarily about performance, hence why the weather service example also uses an additional cache specifically for performance.
Dependencies having to pull in tokio is an even larger issue, indicating that async‘s promise of „bring your own runtime“ is a bit of a lie. Lovely, lovely dependency hell.
> Most bullies already know the world hits back, that's why they are acting out
Not in my experience. There definitely will be some problematic kids, but to the majority of school bullies, I don't think this applies. To recall two of my own experiences:
As a boy I was being bullied by a group of kids. Some day I snapped at them and decided to resolve the matter there and then. I didn't care they outnumbered me. I didn't care if I'd win or lose. I genuinely was ready to fight to the death (lol). But it never came to that. Showing some teeth spooked them and they left me alone after that. I remember the dumbfounded look on their faces. So while it didn't come to violence, the threat of violence scared them off.
On the other hand, when I was bullying a boy (I honestly don't know why), he eventually fought back. That really surprised me and I vividly remember how much respect he gained in my eyes for it. It was humbling. We became friends.
The best thing that can happen to a bully is their victim standing up for themself. Like the person you responded to said: "A boy who bullies needs to learn that the world hits back." The exception to this is kids with sociopathic tendencies (for lack of a better term) - kids that double down on their behaviour despite being confronted with the consequences. How a kid will respond is, I think, more of a function of their personality than the punishment received. But what do I know?
The slowing down thing sounds like a hack needed for engines that don’t give you control over the main loop.
I haven’t tried this yet, but for a custom engine I would introduce a second delta time that is set to 0 in the paused state. Multiplying with the paused-dt „bakes in“ the pause without having to sprinkle ifs everywhere. Multiplying with the conventional dt makes the thing happen even when paused (debug camera, UI animations).
You have some packets of data a, b, c. Add one additional packet z that is computed as z = a ^ b ^ c. Now whenever one of a, b or c gets corrupted or lost, it can be reconstructed by computing the XOR of all the others.
So if b is lost: b = a ^ c ^ z. This works for any packet, but only one. If multiple are lost, this will fail.
There are way better error correction algorithms, but I like the simplicity of this one.
Not too long ago, I used to think that Markdown was the Bee‘s knees. But having been forced to write some documentation in plaintext, I learned that plaintext is significantly more readable than raw markdown.
I think one of Markdown‘s biggest sins is how it handles line breaks. Single line breaks being discarded in the output guarantees that your nicely formatted text will look worse when rendered. I understand there are use cases for this. But this and the „add a trailing space“ workaround are particularly terrible for code documentation.
> But many modern artists challenge these long traditions, creating statues of figures that are fully clothed. Consider Thomas J. Price’s “Grounded in the Stars”: a 12-foot, monumental sculpture of a woman standing in heroic counterpoise, wearing a T-shirt, leggings and comfortable shoes!
Looking at that modern statue, I can‘t help but be bored. It doesn‘t draw my attention. I think that’s because it depicts a normal, everyday clothed person. We see those everyday. It‘s something mundane.
A naked statue is more interesting to me. It‘s less a depiction of a person and more of mankind in general. It has an abstract but intimate quality, inviting to reflect (wow that sounds posh).
The baseline of 0.0 represents the average of all years. Anything above / below the baseline is a (standard) deviation from the average. The blue lines are the individual years since 1991 [1] while the red line is the year 2026.
If a line is above the baseline, then the sea-surface temperature was hotter on that day than average. If below, it was cooler than average.
The year 2026 is an outlier, dwarfing all the others starting around June / July. The Nino 3.4 sea-surface temperature is significantly hotter than any previous year during that time. New record, I guess?
[1]: I'm confused about the two date ranges given: 1982-2026 and 1991-2020. I'm assuming this graph is based on measurements from 1982-2026 to calculate the average, but the lines shown are only from 1991-2020, for some statistical reason I don't understand.