If I make sure to leave at peak commute time I’m pretty I can do that just for Paris-Marseille.

Wait just about 100 days and you can make it Paris - Paris.

rumors

You can remove that word, rly.

On a side note, it’s systemd, no damn uppercase D at the end.

Usually Linux has at least comparable framerates to Windows, if not faster.

CS2 beg to differ.

Holly shit, after looking things up it’s even worse than I thought…

Playing Valorant will need to enable TPM 2.0 and secure boot under windows 11 OS, you have to check that your motherboard is support TPM 2.0 system. (NOTE: If your system unable to support TPM2. 0, the only way that you can play Valorant is change your windows to older version as windows 10.)

Damn, Riot effectively turning PC into console…

Also I’ve read that C# is C++++ (like put those + on 2x2 table, which in turns ressemble a #)

whatever works for you, but what will you comme up with for “un avion” ? :)

Because “people” (my french self included) would just say (most of the time) “la machine à laver” (or even shorter : la machine) and out of context, you’d figure out which of the 2 is actually talked about.

Also, as “machine à laver” litterally translate to “washing machine”, it didn’t even occure to me that it had to be understood as laundry machine, hence why I initially said it was a “she”.

Un lave linge, une machine à laver le linge, un lave vaisselle, une machine à laver la vaisselle. It actually all depend on they way you phrase it. Agreed though. It was mostly for the joke.

It’s a she, because that’s a woman job. Same goes for dish washer !

Also, there are a few words that even french (most of them) would have the gender wrong…

I put my self hosted instance down on purpose and tried to access my phone’s app. It works and I can export to csv or json from there.

The likelihood of my phone & NAS breaking down at the same time seems rather thin.

wait what ?

So you are saying that the following code will keep throwing e but if I used throw e; it would basically be the same except for the stack trace that would be missing the important root cause ?!

try {
} catch (WhateverException e) {
    // stuff, or nothing, or whatever
    throw; 
}