The optimal age to have children is way before you need to rely on frozen eggs (one reason among many being that this process doesn't always work)
Readit Newsyosefk commented on The optimal age to freeze eggs is 19 lesswrong.com/posts/dxffB... · Posted by u/surprisetalk
yosefk commented on Claude Code Remote Control code.claude.com/docs/en/r... · Posted by u/empressplay
Struggled with it also, given up (for now).
I thought coding was a solved problem Boris?
Coding is a solved problem. Problems with the code - these are far from solved, in fact they're multiplying, but coding is definitely solved
yosefk commented on How to make a living as an artist essays.fnnch.com/make-a-l... · Posted by u/gwintrob
As a resident of SF I've only ever heard of fnnch in the context of people hating his art (I still don't understand why). Is it a case of any publicity being good publicity?
Seems like a case of snobbery on behalf of these people. These are nice images but not "high art" which I guess prompts some people to scoff at them
"Ironically, among the four stages, the compiler (translation to assembly) is the most approachable one for an AI to build. It is mostly about pattern matching and rule application: take C constructs and map them to assembly patterns.
The assembler is harder than it looks. It needs to know the exact binary encoding of every instruction for the target architecture. x86-64 alone has thousands of instruction variants with complex encoding rules (REX prefixes, ModR/M bytes, SIB bytes, displacement sizes). Getting even one bit wrong means the CPU will do something completely unexpected.
The linker is arguably the hardest. It has to handle relocations, symbol resolution across multiple object files, different section types, position-independent code, thread-local storage, dynamic linking and format-specific details of ELF binaries. The Linux kernel linker script alone is hundreds of lines of layout directives that the linker must get exactly right."
I worked on compilers, assemblers and linkers and this is almost exactly backwards
When did I say I don't think comp is important?
Thank you very much for your work. I think people envious of someone's compensation don't deserve a response
yosefk commented on What I learned building an opinionated and minimal coding agent mariozechner.at/posts/202... · Posted by u/SatvikBeri
"Also, it [Claude Code] flickers" - it does, doesn't it? Why?.. Did it vibe code itself so badly that this is hopeless to fix?..
yosefk commented on In Europe, wind and solar overtake fossil fuels e360.yale.edu/digest/euro... · Posted by u/speckx
> Solar prices in the US are criminal, protecting oil and gas who bought all the politicians.
It would be worth including control of the people who vote for the politicians by direct investment such as when the oil producing Saudis bought the second largest stake in NewCorps which controls FoxNews controlling the content that influences voters. And, less than ethical control using bots on social media by Russia.
A lot of what influences "solar prices in the US" is controlled by foreign oil producing countries like Saudi Arabia and Russia controlling content and media consumed by American voters.
The list of the oil producers listed and omitted on a given forum in these contexts is always interesting. On HN it is often SA or Russia, and almost never Qatar or Iran.
yosefk commented on Erdos 281 solved with ChatGPT 5.2 Pro twitter.com/neelsomani/st... · Posted by u/nl
> I then gave both proofs to Opus and it confirmed their equivalence.
You could have just rubber-stamped it yourself, for all the mathematical rigor it holds. The devil is in the details, and the smallest problem unravels the whole proof.
How dare you question the rigor of the venerable LLM peer review process! These are some of the most esteemed LLMs we are talking about here.
Of course it is not reserved for library writers - nothing is. But it is not a feature that application writers should worry about overmuch.
std::move is definitely for there for optimizing application code and is often used there. another silly thing you often see is people allocating something with a big sizeof on the stack and then std::moving it to the heap, as if it saves the copying
> So, what are the forces that have determined the current state of C++?
A subset of the language aimed at library writers. As a user of those libraries all these weirdo features are likely to be transparent.
TFA explains how std::move is tricky to use and this is not a feature reserved for library writers