Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)J
Posts
1
Comments
61
Joined
3 yr. ago

I mean no harm.

  • This might just push my fear of targeted ads enough to give in to my idea of a nearly soundproof box for my phone when I'm not using it. :(

  • They got credited for scientific research: link

  • Send it through the earth, you can reduce it theoretically to 42.5ms

    This isn't as ridiculous as it sounds and you just need a neutrino-beam... which has a horrible bandwidth (of 0.1 bits/s) plus the ridiculous upfront cost of running two particle-accelerators for a full-duplex link. (Google it up, this exists.)

  • My favorite so far:

     
        
    $ gdb -ex 'file /bin/gdb'
    run
    corrupted double-linked list
    
    Thread 1 "gdb" received signal SIGABRT, Aborted.
    
      
  • C++

    Jump
  • I once wrote bind_front() and move_only_function likes in C++17. This nearly drove me mad because you cannot refer to a overload set by a name.

    On the otherhand, I can now decipher the template error mess that the (g++) C++ compiler spews out.

  • what the actual fuck. 🤮

  •  
        
    $ gdb -ex 'file /bin/gdb'
    run
    corrupted double-linked list
    
    Thread 1 "gdb" received signal SIGABRT, Aborted.
    
    
      

    Yeah, try debug that.

  • A kernel was released that changed how the hash value got computed for casefolded filenames. (used for better windows compatibility) That kernel then went into production. This unfortunately split some file-systems that supported this into two incompatible versions, breaking the kernel rule 1.

    There might now exist file-systems were created/modified with this bug present that the old/fixed kernels can't understand.

  • *) The only socially acceptable way for a man to cry. /s

  • If I would drink any coffee in that time, (even worse with/or booze) I would be still up the next day by a large margin. :(

  • As much as I like at some time before 14:00 'o clock and then none.

    Caffeine has about 8hrs half-life and blocks a few key receptors in the brain, so it will only mask the tiredness you build up over the day.

  • I was reluctant to take this project, knowing well I would end up deleting nearly all existing code I would have to touch, all while having just mediocre skill writing its successor, if it ever becomes one.

    I can no longer escape from this project, nor do have I will to.

  • "When you do things right, people won't notice and it's like you have done nothing at all."

    Futurama or something something quote likely not word-to-word correct.

  • Sugar is half bad, half good: the glucose part causes no harm and whole body can use it. The fructose part on otherhand is bad and has to/can only be processed by the liver first.

  • Yeah, it feels like I blinked and it's now October already...

    (2024 was and still is a heck of an year for me. I have almost climbed out of the ditch on this year. Yay!)

  • Python is just a pile of dicts/hashtables under the hood. Even the basic int type is actually a dict of method names:

     
        
    x = 1
    print(dir(x))
    ['__abs__', '__add__', '__and__', '__bool__', '__ceil__', '__class__', '__delattr__', '__dir__', ... ]
    
      

    PS: I will never get away from the fact that user-space memory addresses are also basically keys into the page table, so it is hashtables all the way down - you cannot escape them.

  • The short version:

    This means that you reset your password with a 32-character long generated password, which is saved in your vault, PlayStation saves a 30-long password and then you use the 32-long password to log in, which fails because it isn’t the same.

    That password prompt should be scorched to earth.

  • "The kernel runs out of time to solve the NP-complete scheduling problem in time."

    More responsiveness requires more context-switching, which then subtracts from the available total CPU bandwidth. There is a point where the task scheduler and CPUs get so overloaded that a non-RT kernel can no longer guarantee timed events.

    So, web browsing is basically poison for the task scheduler under high load. Unless you reserve some CPU bandwidth (with cgroups, etc.) beforehand for the foreground task.

    Since SMT threads also aren't real cores (about ~0.4 - 0.7 of an actual core), putting 16 tasks on a 16/8 machine is only going to slow down the execution of all other tasks on the shared cores. I usually leave one CPU thread for "housekeeping" if I need to do something else. If I don't, some random task is going to be very pleased by not having to share a core. That "spare" CPU thread will be running literally everything else, so it may get saturated by the kernel tasks alone.

    nice +5 is more of a suggestion to "please run this task with a worse latency on a contended CPU.".

    (I think I should benchmark make -j15 vs. make -j16 to see what the difference is)