Which is not to say that they are necessarily auto-vectorizing. You know wassup when you see vaddsd instead of vaddpd. And ideally you'd use AVX-512 to saturate a modern cache line if you can afford to drop support for the older devices.

older devices, is rather vague, this means intel client chips even as late as panther lake do not support avx512 or avx10

Or runtime CPU detection and dispatch to support both.

The scams do leave voicemails now, and they use voice genAI per the parent comment.

If someone really wants to get a hold of you, they can knock on your door.

Like I ever answer my door lol. But they can leave something in the mailbox, and I'll at least see the envelope in 1-30 days.

Last week I finally had an onslaught of spam voicemails, several in an hour, that caused me to disable voicemail notifications altogether. I'll just check them when I'm expecting something now, similar to mail. My phone app was successfully filtering the calls so I wouldn't see them, but it still got routed to voicemail which then created a notification.

Disable! Voicemails are nothing. If something is important it's delivered via text/app or email.

Voice stuff is just narcissists trying to get their way.

With all the Nigerian princes out there, you'd think one of the bastards would have already made an official claim to the throne.

"cringelord"

I cracked. Had never seen that used before, yet so obvious now in retrospect. Pure poetry.

Not sure what's worse, if the AI slop content, or the AI code slop that makes the site consume 100% of a single CPU core (and if you enable GPU rendering on the browser, CPU usage is still significantly above zero.)

> I'm provably doing the minimum amount of work possible.

That is a very bold claim to make for the amount of render code generated by the LLM. It's not obvious what the critical path even is, which is what would bound the latency. And I mean actual code, not just some informal description of what happens.

If you say 'provably', you should offer the proof. In Lean perhaps? But in English is also ok.

these days on HN, if you oppose someone, you get dead-flagged.

I vouched for your comment, as I find it perfectly 'not agreeing' answer.

It wasn't me flagging, by the way.

The burden of proof also falls on the person making the claim.

Sorry, but you simply prompted an LLM and didn't even bother reviewing the output per our other discussion about pthreads. I'm not sure you can claim to be an expert, let alone put your opinion on the same level as mine.

Why are you using pthread instead of std::thread?

One advantage to using pthread is the ability to call pthread_setname_np to name threads and thereby make debugging easier. Granted, you can call it with std::thread by using std::thread::native_handle() to get the pthread handle, but you're still using a non-std::thread API.

I see, I wasn't aware of that one. Typically I'd assign an ID, but yeah, names make things easier.

I guess I just didn't notice. In any case, it wouldn't have been std::thread, but https://github.com/pg83/std/blob/master/std/thr/thread.h from my bike lib!

What do you mean you didn't notice? I saw another comment about Claude below, are you not even reviewing the output?

I just browsed the project for two minutes and it's one of the first things I noticed. std::thread is more portable (Windows, if anyone cares) and allows you to pass in a lambda, which keeps the code local and also has the compiler generate the closure for you instead of having to pass function pointers and void* captures around. I don't see any advantage to using pthread directly.

> What do you mean you didn't notice? I saw another comment about Claude below, are you not even reviewing the output?

Of course I looked at the LLM output, but people, uh, make mistakes and can miss something.

> std::thread is more portable (Windows, if anyone cares) and allows you to pass in a lambda, which keeps the code local and also has the compiler generate the closure for you instead of having to pass function pointers and void* captures around. I don't see any advantage to using pthread directly.

These are obvious things, and the objections to them are equally obvious. For example, std::thread is an additional level of abstraction over pthreads, which, in essence (not in form), gives me nothing. And I don't care about Windows, really.

I thought it was general knowledge that growing up with animals, not necessarily in a farm, boosts your immune system for life with all the (good) shit you get exposed to.

Interesting use of DoF, hadn't seen that in an isometric game. Art looks really good too.

The best part is that the era isn't gone; you can buy those and the games, and it's not even an expensive hobby. And people also know how to / can repair them.