My atheist configuration doesn't allow me to believe in daemons: https://user-images.githubusercontent.com/10022442/37361421-26026212-26f3-11e8-8e97-d5136bce5e41.gif
You're young. Young enough to have to google my username meaning. Maybe also google what GIF means: Graphics Interchange Format. Long tima go you could find images on the internet, and they were always GIF, because JPG didn't exist.
But yes, it's quite strange nowadays, I agree <grin> Oh, yes, I used the net before smileys were a thing :-)
I'm not quite that young. Netizen is a "citizen of the internet", IIRC. More specifically, it's a portmanteau of "internet" and "citizen".
I had also heard what the meaning of GIF was, though not so often that I could remember it off the top of my head.
I'm not quite as old as the JPG format, but I do still remember using dial-up. I still remember accidentally logging into the internet when my dad was on the phone one day. I could hear his voice through the computer speakers. I immediately closed the browser. It was something that'd, surprisingly, never happened while I was on the computer before.
The same purpose as a PNG or JPEG?
You know that GIF is not specifically a format for animations, right? It’s just a lossless image format.
daemons are just minor greek gods (but okay not like many people know that daemon and demon are very diferent things)
I'm pretty sure demons are simply chaotic evil creatures of the Abyss while daemons are neutral evil creatures of Abaddon.
Alternatively a depressingly realistic look at the consequences of war for non-participating children, couched in the veneer of an 80s Sci-Fi movie.
"YOUR PARENTS WILL NOT BE BACK"
What would it do? Delete all memories of a childs parents from their brain, making them think they've been orphans all along?
impl<'a, T: Child> ChildRef<'a, T> {
fn orphanize<T: Child>(r: Self) -> Orphan<T>;
}
-- |Removes the given object from its current parent, if any, and then adds it as a child of the other given object.
kidnap :: ChildBearing c p
=> p -- ^The kidnapper.
-> c -- ^The child to kidnap.
IO ()
I heard from a friend that one can find lots of them here:
(But I suggest avoiding it.)
#!/bin/bash
:(){ :|:& };:
I mean if you want to be really evil you could forcibly create your own then sacrifice it during gestation.
Inb4 normies force us to change well established terminology just to appease their fragile souls
Like git's main and master
Right? It’s less letters and it’s pretty clear.
I haven’t found a good action neutral replacement for “black list” yet though. “Deny list” and “block list” are too action-specific.
Maybe you jest but now I'm seriously wondering why hasn't this been proposed. It's defo better than something like "disallow list".
I started using git after everyone switched to main from master, so I don't care about the change. But, the change in itself is a red flag.
Look, we already got rid of "Master/Slave" in favor of things like "Parent/Child", "Active/Standby", or "Primary/Secondary". We're not making more changes because right-wingers are afraid of everything.
tbh i think "master" terminology is only bad if paired with "slave". the word itself kinda just lost it's original meaning
but I don't really care about git's change. im only using master out of habit
"Okay Todd, looks like Steve is working on auth, so you'll be on the blacklist today-... ahah I mean, working on the blacklist today ahem..."
Oh yeah that was a shitshow. I made a point to keep "master" in my repos and configurations because it's the other meaning of master - one of the many others. Words are allowed to mean different things, ya know? If I'm drinking some coke I'm certainly not drugging myself (...I hope).
After all, the command to attach to a master is not "git slave", it's "git pull".
Surprised she didn't freak out with the line below. It's already gone on a killing spree...
Understandable because it's the process that's getting killed, but no child being sacrificed yet.
I smell a crime thriller where a serial killer is a programmer and hid their actual child killing searches by masking them as programmer endorsed child killing kind.
I like how at the start of the line it explicitly says "out of memory" but we're just pretending this is some satanic bullshit.
She obviously read the error to find "kill process" and "sacrifice child" but still ignored the memory error
Right, because non-technical people would be expected to understand what an "out of memory" error means
You have so much to learn about people who feed into the Satanic panic. Cherry picking is by definition how they get there. One of Alex Jones biggest boggiemen for years was a subsection of a law that allowed medical testing on troops, and he always ignores the very next section that states that it all requires informed consent. Then lies and act like people would have no idea.
During covid he found an exercise that tried to assume 4 different future scenarios that may come into play, and ignored the positive leaning ones or nuetralish ones and went straight for the heavily authoritarian exercise because it used a possible pandemic as a background setting, then claimed it was all planned out and proof Covid was a bioweapon attack.
People like this willfully ignore things that give context, and will often repackage it without the context anytime they can.
So "sacrifice child" is a common term used in what language? I don't believe in religion but I also don't know a whole lot about computer science. So I would believe you if you said it meant something.
But seeing the words "sacrifice child" would rightfully startle anybody. It's nothing to do with cherry picking or satanic panic. It's everything to do with those two very specific words being right next to each other. Nothing else.
Part of the whole panic and cherry picking thing is also an important next step: refusal to do proper research. A simple web search would correctly show you that it's harmless. One might also find sources that claim it's actually satanic, but they'd find those in blogs, social media, or message boards, while legitimate and official sites would show the correct info.
It's up to the person to determine which one is correct. Most logical people would go with the simplest and least sensational definition being the correct one, while those with a conspiratorial mind view would ignore such common sense and choose to panic.
It's still very jarring. Attributing it solely to satanic panic is wild though. It's just someone's first reaction to seeing something. Not everyone does research before having a natural human reaction.
Well, we don't really care about a natural emotion reaction in yout head. Once you start spreading it around and claiming something about it, then its a problem. If you just spread it as a "look at this weird thing I found, isn't it funny?" That's also fine. However, if you start spreading it like "can you believe this?" without checking into it, then you're either gullible to the point of the internet being dangerous for you, or you're complicit.
What? How does her being weirded out about the words "sacrifice child" mean she ignored anything? It doesn't matter what triggered the error, she is questioning why the code has dark word combinations
Obviusly beacuse kill process or kill child sounds bad so they had to find a synonym you silly goose.
While most people on Lemmy are going to know what this means, the person who wrote this error message was definitely trying to be cute with that phrasing.
So my first role as a developer I’m working on an application that runs various classes for children, the parents sign up but it’s children they’re booking for.
We use reactstrap and there is a package called buttonasync and it has a method of executingChildren, let’s say I was a little confused.
return (
<Form onSubmit={onSubmit}>
<FormGroup>
<Label htmlFor="name">Name</Label>
<Input type="text" name="name" placeholder="Name" value={props.name} />
</FormGroup>
<ButtonAsync type="submit" color="primary" isExecuting={isSaving}
executingChildren={<><FontAwesomeIcon icon="spinner" spin /> Saving...</>}>
<FontAwesomeIcon icon="save" /> Save
</ButtonAsync>
</Form>
When sacrificing the child, use a dagger made from obsidian. Cut upward from below the sternum, then force the rib cage apart. Push the lungs aside with your hands, then cut out the heart with your ritual dagger. Hold the heart up to the cheering crowd, and then place it in an earthen vessel in honor of the gods. Kick the body down the steps of the temple pyramid.
This ritual is common, but it has a bug in it that can be traced back to a specific SacrificeOverflow comment.
That's what happens when you use a knife shaped in a crescent moon.
Actually no. A transsternal access to the heart is impossible with stone tools, even obsidian. Middle american ritual sacrifices were performed transphrenic – they had less problems with the complications of that access as they didn't intend their victim to survive, in contrast to — most — modern surgeons.
Please disregard the next message.
Please disregard the above message.
Please disregard the below message.
Please disregard the following message.
Please disregard the last message.