they said that AI would take programmers’ jobs, but in reality it did the opposite :D

easy, just replace system32 with /usr/bin

Correct, we should move slowly and break things

What is this referencing?

that’s an upside, screw leg hair

Oh THAT’s what the random freezes were. Got them sporadically on my Arch machine for a couple of years, and never figured out exactly why. (Now I’m using a different laptop that still has AMD graphics, but I haven’t got a freeze yet.)

Because I like compiling everything from source for a 0.2% speed improvement

Where’s the funny. If you don’t fix an issue, it’ll lead to more issues? Is that what it means? No AI slop please

my best guess: system("bash -c 'echo \\\"¯\\\\_(ツ)_/¯\\\"'");

which will get parsed as: bash -c 'echo \"¯\\_(ツ)_/¯\"'

which will run: echo "¯\_(ツ)_/¯"

and since echo just prints whatever was given to it, it’ll print "¯\_(ツ)_/¯" with the quotes

It’s thing! Omni-man says ‘thing’, not ‘part’. I’ve seen this meme format for a few years now and I’ve only just realised it’s a misquote after watching the show. Completely irrelevant nitpick I know but some people might appreciate it.

Wow, massive red flag. How quickly did you quit?

Strawbery

And 90% of the time, n is about 3

The line causing the memory leaks is actually the lack of a line: free().

did you mean to comment this here?

At a PV node, do not cut off from any TT hit.

The SPRT result of this may be different than before thanks to LMR.

Bench: 5212899

hey, you did ask

If it gets comitted to master, TODO means never do.

'The image cannot be displayed because it contains errors.`

Oh I get you. No idea tbh.

Actually vim has swap files which it saves to when you make any edit, whether you save the change or not, meaning you shouldn’t lose any work even if you kill -9 vim on unsaved work.