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

  • 0 Posts
  • 221 Comments
Joined 2 years ago
cake
Cake day: August 13th, 2024

help-circle
  • In the C programming language. Or do you mean which C project specifically? Because as Technus surmises in their response, it’s usually a better idea to set up aliases (typedefs or heck, even #defines) so that you’re offloading some of the mental strain keeping track of the layers, and that’s likely to be what happens in production code.

    But the underlying data type is still T***.




  • My local buses used to have something on the screens that would occasionally get stuck in a reboot loop between something that looked a bit like BIOS text and then MS-DOS. This was over a decade ago though. The screens were designed to switch between different views from the bus’s various cameras. I think the idea was to discourage anti-social behaviour by reminding people they were being watched.

    But I guess the contract ended and things proved too expensive or too hard to maintain because the next batch of buses didn’t have screens in them. The cameras didn’t go anywhere though.




  • palordrolap@fedia.iotoProgrammer Humor@programming.devdo not
    link
    fedilink
    arrow-up
    10
    arrow-down
    1
    ·
    1 month ago

    But if you do decide to do this, and I should stress that this does not constitute a suggestion to do so, make sure to go out in clearly identifiable footwear and clothing and with no head or face coverings so that the camera can get a good look at you before it dies, you filthy, filthy vandal.




  • palordrolap@fedia.iotoProgrammer Humor@programming.devStill valid
    link
    fedilink
    arrow-up
    104
    arrow-down
    1
    ·
    1 month ago

    If you’re talking about applications that can be made to act how their namesake predecessors did 30 years ago, sure. The Unix mindset is all about that.

    But don’t be fooled into thinking that anything on a modern Unix-like system hasn’t been modified, patched or rewritten from scratch at some point in the last 30 years. More than once. Even /bin/false has a changelog.





  • I’m about 50/50 on grammar errors. They bother me either way, but sometimes I feel the need to correct them and try to explain why.

    Today I seem to have worded it in a way that’s rubbed people the wrong way. It has gone better. You win some, you lose some.

    And yes I know I sound like an LLM. I used to not be able to communicate my ideas at all (flashback to not being able to string a 500 word essay together at school) but then I got a job working technical support and I had to figure out a way of getting my ideas and explanations across. And this is now how I communicate, for better or worse.

    Unfortunately, LLMs learned how to communicate in a not dissimilar way. And so we sound alike.


  • *whose

    “who’s” is “who is”[1] or “who has”[2], and it can be wrestled into a possessive if you make “who” all or part of a name[3], but it’s the wrong sort of possessive for this context. If you really want the possessive form, it ought to be phrased “which person’s”, which is mostly what “whose” means.

    (An actual linguist would speak more about the genitive and how it works in English, but I’m not as capable.)

    [1]: e.g. “Who’s there?” [2]: e.g. “Who’s let the cat out again?” [3]: e.g. “This is you-know-who’s box of tricks.”


  • Pipewire is newer and emulates PulseAudio so that it can be used as a drop-in replacement. There’s literally a command called pipewire-pulse related to this.

    It makes me wonder if they really have both installed or are mistaking Pipewire’s emulation for an active PulseAudio installation, and so it’s just Pipewire that’s acting up.

    I’d say reboot, but being in space might be one of those times where that’s a non-starter. In which case, they’re going to have to get their hands dirty unpicking system hooks and trying to reattach them all again as and when Pipewire’s working again, assuming it doesn’t do that automatically.

    I never had a problem with either Pipewire or real PulseAudio back when that was current. I had motherboard sound physically pop, requiring the purchase of a separate sound card, but never a driver issue, so I can’t even imagine what might be going on.




  • At a guess, the counter goes up by fractions of a day internally, but it’s reset by subtracting the integer part, rounded.

    The original version wouldn’t have had the rounding but they “fixed” that after the first time they did a reset and it went to 1 not 0.

    As to why they wouldn’t just set it to zero, well here we have the joke under a microscope and it’s struggling to stay alive. Put the scalpel down.