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

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

Is on kbin.social but created this profile on kbin.run during a week-long outage.

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

  • 0 Posts
  • 56 Comments
Joined 26 days ago
cake
Cake day: June 4th, 2024

help-circle




  • anaemic* (Sorry, that bothered me for some reason.)

    As for capture groups, you’ll have to find another way. Perversely, perhaps BusyBox continues to be included on certain systems because they know that the extra space is required for the code that works around BB’s shortcomings. That sounds asinine until you realise that “solving the problem properly” most likely leads to that one XKCD comic about the proliferation of competing standards.

    At worst, multiple sizes of BusyBox itself.






  • Other than the psychopath angle, there’s also those who are mentally ill and/or delusional and believe they’re terrible people when they’re not far off average, maybe even better.

    Likewise, perfectionists, but maybe I’m repeating myself.

    Got to hope that you’re not right for their sake.

    Personally, I’m hoping for oblivion. Like it was for the billions of years before I was conceived, I assume, not that it’s possible to remember that.


  • Fun fact: The past tense of “wend” was once “went”, but that was co-opted for the past tense of “go”, and the past tense of wend is now “wended”.

    “But what was the past tense of ‘go’ before that?”

    Kind of hard to tell what it would be now, but “goed” does seem likely - like we might have said as toddlers - but irregular “yode” / “yoed” is closer to the old form and is also possible.

    Evidence from other Germanic languages as well as “do” becoming “did” suggests a less likely “gid”, “gig”, “ging” or even “gang” (compare “sang”).




  • JavaScript, like some other languages of the time, was designed with the Robustness Principle in mind. Arguably the wrong end of the Robustness Principle, but still.

    That is, it was designed to accept anything that wasn’t a syntax error (if not a few other things besides) and not generate run-time errors unless absolutely necessary. The thinking was that the last thing the user of something written in JavaScript wants is for their browser to crash or lock up because something divided by zero or couldn’t find an object property.

    Also it was originally written in about five minutes by one guy who hadn’t had enough sleep. (I may have misremembered this part, but I get the feeling I’m not too far off.)


  • palordrolap@kbin.runtolinuxmemes@lemmy.worldbin or bin??
    link
    fedilink
    arrow-up
    39
    arrow-down
    1
    ·
    8 days ago

    I don’t know about that. Non-binary files have been put into bin directories for decades at this point. (Feel free to marvel at the analogy.)

    Delete the contents and it’s not just binaries going to the bit-bucket.

    The joke here is more “Tony Lazuto said to execute these files.”


  • An analogy:

    My Swiss Army knife has a screwdriver on it. It’s nice to have, and I even used it recently.

    It juts out perpendicular to the middle of the knife’s body though, making a literal " |- " shape, so for many applications it’s too awkward for the job.

    I also have a more traditional screwdriver. As and when I come to build a new PC, I don’t think I’ll be using the one on the knife.


  • xterm is a terminal emulator, not a shell. Anything that produces a terminal-compatible text stream can be started as the first program.

    e.g. xterm -e nano, assuming you have the nano editor installed, has no instance of a traditional shell (e.g. bash, zsh) running between the xterm and the editor, but the editor still works.

    You could argue that makes the editor itself a shell of sorts, because it’s interactive and you can do things with it, but it’s still not the xterm that inherits that title.



  • I’d say it’s more like setting up a handler for a callback, signal, interrupt or something along those lines.

    Function declarations by themselves don’t usually do that. Something else has to tell the system to run that function whenever the correct state occurs.

    That doesn’t account for unconditional come-froms.¸but I expect there’d have to be a label at the end of some code somewhere that would give a hint about shenanigans yet to occur. Frankly that’d be worse than a goto, but then, we knew that already.