Some middle-aged guy on the Internet. Seen a lot of it, occasionally regurgitating it, trying to be amusing and informative.

Lurked Digg until v4. Commented on Reddit (same username) until it went full Musk.

Was on kbin.social (dying/dead) and kbin.run (mysteriously vanished). Now here on fedia.io.

Really hoping he hasn’t brought the jinx with him.

Other Adjectives: Neurodivergent; Nerd; Broken; British; Ally; Leftish

  • 1 Post
  • 260 Comments
Joined 8 months ago
cake
Cake day: August 13th, 2024

help-circle
  • True. I think of it more as a semantic shift. In the old days, processes would actually quit and some other process would resurrect it as necessary, but then someone had the idea of having some processes catch the HUP and do all that itself without actually bothering any other processes.

    And the implementation might actually involve an exec of the process’ own executable, meaning that it actually does self-terminate, but it leaves a child in its place.


  • palordrolap@fedia.iotoComic Strips@lemmy.worldThe Fun
    link
    fedilink
    arrow-up
    1
    ·
    46 minutes ago

    So I reread it and it says “P follows Q”, which I (mis)read/(mis?)interpreted as “P follows from Q”.

    I don’t remember if “follows” was ever used for forward implication in this way when I actually did a logic course, but it was a few decades ago now. Maybe it was.

    There’s also that the usual joke in this category is that in basic logic, false implies true, which seems to be the punchline of the joke in the comic, just with the arrow backwards.



  • palordrolap@fedia.iotoComic Strips@lemmy.worldThe Fun
    link
    fedilink
    arrow-up
    3
    arrow-down
    1
    ·
    1 hour ago

    Isn’t that implication arrow backwards?

    “P follows from Q” is P ⇐ Q

    Maybe that’s the joke, though.

    EDIT: The text says “P follows Q”, which my brain apparently corrected to “P follows from Q”. These are not the same, and I’d argue that “P follows Q” is problematic as a phrase as a result. Grumble grumble.


  • Well, yes, but actually no. It’s an old analogue “portable” 14" CRT TV with push button channel controls. Haven’t had it switched on in probably a decade at this point, and even if I did, all TV is digital here now, so it wouldn’t be able to show anything without a lot of outside help.

    There’s a VCR under it that used to serve some of that purpose, but that’s also analogue only, doesn’t play tapes any more and the remote control is busted, so yeah, no TV.

    That said, I adopted the philosophy of the bedroom only being for the main bedroom activities a while ago. You know. Dressing, undressing, testing the mattress and sleeping. This may be your husband’s line of thinking.

    I moved the computer out of there for that reason too. The TV and the trolley it’s on only remained because it’s in use as a clothes horse.





  • For most intents and purposes, they’re no more dangerous than a star of the same mass in the same place.

    There’s also the theory that our universe could be the inside of a black hole in a higher-order universe.

    Of course, trying to imagine the size of our universe, let alone an entire hierarchy of them where ours may just be itself an insignificant speck, might cause more doom sensation than less. Do with this information what you will.




  • To steal an idea I had on something similar once, perhaps on an entirely different site, there’s also where the wings come from in the first place, literally and figuratively.

    The equivalent structure to a bird’s wing in humans is the arm and hand. Does this new wing take the place of the forelimb as it does in birds or does the wisher necessarily become a six-limbed creature?



  • From the naive perspective it’s looping infinitely and it ought to be infinitely old because there’s no “first loop”. Depending on the laws of physics, proton decay could make the pizza slice literally impossible.

    Given that it clearly exists and has no rot let alone deep-time decay, I posit that it spontaneously appears/renews in panel three, away from the boundary break, as some kind of near-infinitely improbable entropy break.

    He thinks he’s discovered panel time travel, but it’s far weirder than he thinks.


  • Can only speak for myself, but I think backspace is probably one of my most used keys, the number of typos I make. Generally, I don’t miss these*, but when proofreading or rewriting parts of comments I occasionally leave a word in from a previous iteration or take one out that I meant to leave in, throwing a wrench into the flow.

    I can easily imagine that for some people that goes to another level and they might be too tired or stressed to be able to even notice, let alone fix the mistakes they make. There’s also some level of short attention span going on and people may not be bothered to fix it because they have to be off to the next piece of content or contributing elsewhere.

    * The spell-checking red squiggly underline admittedly being something of a crutch. I’ve noticed an increase in the number of longer or more obscure words that I’m sure I was getting right before but now not so much. And about once a day, on average, I reckon, I reach for right-click to figure out precisely what I’m getting wrong because I can’t figure it out.

    Most of the time, I’ve missed a letter or am woefully wrong, but very occasionally it’s not in the built-in dictionary and online dictionaries basically say it’s fine. And the-e-en I rewrite to avoid the word anyway. Not everyone’s going to do that.



  • Perl was originally designed to carry on regardless, and that remains its blessing and curse, a bit like JavaScript which came later.

    Unlike JavaScript, if you really want it to throw a warning or even bail out completely at compiling such constructs (at least some of the time, like this one) it’s pretty easy to turn that on rather than resort to an entirely different language.

    use warnings; at the top of a program and it will punt a warning to STDERR as it carries merrily along.

    Make that use warnings FATAL => "syntax"; and things that are technically valid but semantically weird like this will throw the error early and also prevent the program from running in the first place.


  • Well, you see, Perl’s length is only for strings and if you want the length of an array, you use @arrayname itself in scalar context.

    Now, length happens to provide scalar context to its right hand side, so @arrayname already returns the required length. Unfortunately, at that point it hasn’t been processed by length yet, and length requires a string. And so, the length of the array is coerced to be a string and then the length of that string is returned.

    A case of “don’t order fries if your meal already comes with them or you’ll end up with too many fries”.