Wrapping a value in a mutex just makes sense. After learning a bit of Rust I made a similar mutex wrapper in C++ when I had to protect a class member in a C++ project. I just had to change the type in the declaration, and bam the compiler tells me about all places this member was accessed. Much easier than using some buggy 'find all references', potentially forgetting a few places.

I think the author of the article just haven't understood how to use the ? operator yet, and don't think they deserve being called "utterly incompetent" for it. Whether something is a monad or not is not necessarily something a programmer should have to think about on a daily basis IMO.

I just think of rust errors as a tagged enum with either a value or an error. And the ? operator as syntax sugar for returning if something was an error. IMO that simple understanding is sufficient to do error handling in Rust. I don't think we should gatekeep programming behind some intellectual barrier of whether or not you understand category theory. I certainly don't understand what a monad is, but I can still write working software and do error handling without unwraps.

Oh that's good then. I think they stopped using whitelists a while ago, so if it is slotted you can probably replace it with anything. Maybe they reversed course on soldered modules then, or perhaps it only applied to some models. I looked into specs of the T16 at some point, and that one had soldered wifi module.

A lot of the modern thinkpads have the wifi module soldered to the motherboard nowadays unfortunately. Sad that they would use these crappy realtek cards in the first place as well.

Yeah the thought is that as long as my patch applies without error, I would get the latest kernel automatically built and can just update my laptop normally with pacman. And since I have a server anyways I might as well use it to compile the kernel at night. I'm also thinking of doing the same with some aur packages as well.

The scary thing about this is thinking about potential undetected backdoors similar to this existing in the wild. Hopefully the lessons learned from the xz backdoor will help us to prevent similar backdoors in the future.

Until meta starts to slowly block small instances and we end up with the next email. Technically federated, but controlled by a few large corporations that dictates the block lists. Let us block them first so we get to define what the fediverse should look like, not them.

It will go brrrrrrrt¤gdføTJwrgt65&<)5½$¥[[¥½{2ahgfh Segmentation fault (core dumped)

I know how to fix this!

bool IsEven(int number) {
    bool even = true;
    for (int i = 0; i < number; ++i) {
        if (even == true) {
            even = false;
        }
        else if (even == false) {
            even = true;
        }
        else {
            throw RuntimeException("Could not determine whether even is true or false.");
        }
    }

    if (even == true) {
        return even ? true : false;
    }
    else if (even == false) {
        return (!even) ? false : true;
    }
    else {
        throw RuntimeException("Could not determine whether even is true or false.");
    }
}

If I'm at 127.0.0.1 why would I need to wear a 255.255.255.0?

That kinda sounds like a bad cable. I've had the same issue with both HDMI and DP before and it was solved with a new cable both times 🙂 Display cables are quite hit and miss when it comes to quality.

EU is the real MVP. Hoping that a few more years now and we'll have iphone with USB C, app sideloading, user replacable battery. I've never owned an iphone before but if that happens, I might consider one.