Every use of "fuck": > So, you can see my Firefox is in Italian, but you can see that it automatically detected that the page is in French and it is suggesting

Every use of "fuck": > So, you can see my Firefox is in Italian, but you can see that it automatically detected that the page is in French and it is suggesting me to translate it to Italian. I will change it to English. Oh, fuck. > The reason for that is because there is so many ways to extend or to define an architecture, and there is some really fucked up things that can be done in so many architectures > We don't measure RSS because it measures anything useful we measure it because it's really fucking easy to measure. > There were a few customers that didn't respond, but at some point you just have to decide to. Don't give a fuck. > Computational storage, what the fuck's that? > like on MacOs you can have a recovery key, on Windows you can have a recovery key, and this is what we should do here as well, right, like use TPMs absolutely, and then hide entropy recovery keys that things are fucked up, things are fucked up > we get money, we invest in open source, and then we have the problem that what we do in open source could be reused by non-European companies. And thinking, oh, my God. Oh, that's so fucking wrong. Why do you do that? > So, you know, if Monty is not screaming at me saying you are fucking moron, Peter, that is not how it is, then probably I am not doing my job properly. > I'm going to wail and gnash my teeth and hope it doesn't happen in practice because at the moment, you know, something like EDK2, to be clear, by the way, I don't give a fuck about non-free firmwares > Is there anybody here who doesn't know what a kubelet is? Okay. The kubelet, oh, you fuck, anyway. > So for now we're targeting your own CA so you can just say fuck it, I will enroll my own keys to the firmware. > So one of the idea is to start to come to a more predictable fashion, which is one major API break and API break every year around December, January, so we're in February, and we fuck this year. > It's really not sure whether we are going to be able to do that because you're transpiling assembly. Like, what the fuck are you talking about? > your problem was where you called, in this case, pop on an empty stack, and not the completely pointless unwrap in there, because you want to know where you're fucked up and not here, obviously. > So if it is, then say, say like, this is fucking wrong, Peter, you know, so I can fix my slides when I talk next time, I have the wrong stuff, right?