Send help
30 comments · 98% upvoted · source · other discussions
30 comments · 98% upvoted · source · other discussions
[removed]
Done, what’s next step? One is screaming, should I do something about it?
[removed]
import moderation
Your comment has been removed since it did not start with a code block with an import declaration.
Per this Community Decree, all posts and comments should start with a code block with an "import" declaration explaining how the post and comment should be read.
For this purpose, we only accept Python style imports.
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.
import moderation
Your comment has been removed since it did not start with a code block with an import declaration.
Per this Community Decree, all posts and comments should start with a code block with an "import" declaration explaining how the post and comment should be read.
For this purpose, we only accept Python style imports.
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.
Is having 2 kids like managing 2 threads that are both modifying global variables?
constant race conditions
People claim your life changes when you have a kid, I think it changes more having that second kid.
Time complexity of parenting is O(n2)
that was also my experience, so hard to divide attention, be there for both, staggering change that was
Have you considered rewriting your kids in Rust?
What?! If anything they need to be deoptimized, I need to rewrite them in something like Java...
There always one option: killall -9 kid
You should have done the appropriate thing for a low-level programmer and never have gotten a girlfriend in the first place
That's small-time, try 4
kids are just asynchronous agents. Probably running random policies
Well, duh. Threads in a multithreaded program do exactly what you've told them to. Kids do exactly whatever they want no matter what you've told them to do.
When you fork it returns the childrens' PIDs just save them to an array and you can loop whenever to wait for them to die.
Now wait until you learn about how a daemon is summoned implemented where you purposefully make a sacrificial child who itself will spawn a child only to kill itself so its child is an orphan and gets adopted by init.
Although it sounds like this is no longer considered (morally) correct.
Until it deadlocks.
Cellular tracking devices? Or do you want them to stay around?
In my fucking soul OP... Fucking in my sooulll
Did you set your kids to be dameons?
At least there's a notion of shared objects in memory for a multi-threaded program.
There's no notion of shared objects between my kids.
Because threads typically dont have randomly things stuck in their nose
AlphaSparqy 26 points · Oct 2022
assert (noseObjectCount=0);