719 karma · joined February 11, 2025
If someone really wants to get a hold of you, they can knock on your door.
I cracked. Had never seen that used before, yet so obvious now in retrospect. Pure poetry.
The burden of proof also falls on the person making the claim.
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.
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.
> Prompt: but I don't have enough money to save, I can barely make ends meet.
> AI: I see the problem now---If you don't have enough money to save, and reducing your expenses is not an option, then the answer is clear: make more money.
Also, I see no mention of alignment in the post. I understand x86/AVX2 likes your load/stores to be aligned, even if it technically allows unaligned access.
Does a given plain image always result in the same encrypted payload?
When you have concentrated power and make a living out of fucking around with everybody else, you seed hatred.