What produces this Iranian "mercy" at a time when Iran is extensively bombed, if not a combination of defensive and offensive capabilities providing escalation dominance?
If they strike desalination plants, Israel/us can do the same … really mass casualty event could follow.
And they might, at some point the Iranian gov might feel desperate enough to be like “fuck it, we have nothing to lose” … Dubai could end up with a lot more graves.
Almost all of their water comes from these plants, and humans can’t survive without water for more than 3 days …
There are reserves/stores sure, but how long will they last, and which part of the population do they cover? In a week you could have thousands of civilians dead on both sides.
So MAD keeps things in check.
I think this is whaly Iran has invested so much into rockets - they are very ineffective at providing decisive military victory by themselves, but without them, Iran will be at Israel’s mercy, and they have proven to not possess that in great amounts lately
My parents and my spouse's parents were all in their late 30s having children, now we're in the same position due to infertility and now finally going through IVF. We're happy it's working but at the same time it's sad knowing they'll grow up never really knowing their grandparents.
The grandparent situation is sad af. It's also pretty sad being a mid-40s year old dad that doesn't have the energy to keep up with their kid. I pitched a little league game yesterday and it wiped me out. Also, the fact I (and you) will not know our grandchildren very well also is quite sad.
If my son has his first kid the same age I had him, I'll be in my 80s when that kid is starting little league (or that age). Then, factor in the fact that I don't know of any men in my family that have lived past 80 and it gets really grim. They were all heavy smokers and drinkers I remind myself with fingers crossed.
The most sad part for me, is I realized by delaying parenthood - I was just being selfish - and the net result is I minimized "shared time on earth" with the person I love the most. It's easy to say I wouldn't have been a good parent or I wanted X job/income first, but it's all just excuses and selfishness.
As a soon to be father, all i can say is don’t do this to yourself man! Remember to give yourself grace and kindness. You made what you thought was the best decision at that time. Maybe it was sub-optimal, but don’t try to min-max life. The “what if” game can be a fun game if it’s done with curiosity, but don’t let it consume you. just isn’t worth it.
>by delaying parenthood - I was just being selfish.. I minimized "shared time on earth"
Exactly. My advice to anyone is not wait. If we hadn't, we would have found out sonner that we needed to go through that process. It's not a "wake up and schedule an appointment tomorrow" kind of thing, it's a treatment of last resort and you can burn years trying, going through evaluations and alternatives first.
Yeah I give same advice, if you know you want kids and found your partner just start soon. We didn’t have many fertility issues just weeding out some unfortunate genetics, but I’ve seen people try for years and it’s really taxing on both the individual and relationship.
The stuff we weeded out was on my wife’s side and the boy ended up being my clone. We joke about it as if we weeded out all of her genes. Even small things like his cowlicks and how his teeth are coming it are exactly like mine which I never would have expected to even be possible (I never gave it much thought tbh)
If you had kids earlier, you wouldn't get more time with the specific person you love that is your son, you'd get more time with a different son. No doubt you'd love your counterfactual son too. But you shouldn't feel bad for having done any wrong by your real kid. This is the only timeline he could exist in.
Bit of a thorny philosophical argument, maybe, but reasonable in this case.
Have considered that as well but shared time with that person would have been more and I would be none the wiser to the actual timeline, so I feel it’s appropriate to treat them as the same “child” instead of theoretical kid vs actual kid and how I’m happy I waited because this kid is so cool, pretty sure I would have felt the same towards the other kid (who knows maybe not but even if he was a jerk of a kid I’d assume a delayed child would have also been a jerk too)
> ...but shared time with that person would have been more
Sticking to the philosophical arguments, having the kid at any other time, even earlier would not guarantee more time with them. It would have drastically shifted your life events which could include ones that possibly shorten it.
Time and guarantees are oil and water, it’s without saying. I don’t even know if you’ve lived long enough to witness this message I’m writing. I’m writing it anyway.
Maybe he was born 10 years earlier and I die in a car crash on the way to the hospital. It’s possible of course I only am alive because I wasn’t on the way to the hospital. While I agree with you on a philosophical point, sure, the fact is I was the one actively choosing to not have kids yet and waiting for some later date. So, I was in much more control of the situation than this philosophical hypothetical or alternate timeline. So, having regret or sharing what I learned from choices I have made still seems like the best choice. I don’t live by thought exercises.
But you live with regret and rumination and thinking up possible future scenarios; that and "living by thought exercises" are two sides of the same coin -- if not the same side. Which is what the argument was meant to playfully point out, in its round-a-bout philosophical way. You can get up to thinking of all the sci-fi timeline altering stuff of the past the same as you can carry regret from thought exercises directed toward future events, thus getting in your feels and self-berating.
It is all thought exercises. The other option is to release the burden of guilt and simply enjoy the timeline you have now. Kids sense these things that their parents carry. Anyway, in no way was I implying your experience or feelings or sharing is wrong or judged
"Coding" is solved in the same way that "writing English language" is solved by LLMs. Given ideas, AI can generate acceptable output. It's not writing the next "Ulysses," though, and it's definitely not coming up with authentically creative ideas.
But the days of needing to learn esoteric syntax in order to write code are probably numbered.
I searched for some pictures. The first couple I came across looked like the result of a prompt to an AI: "generate images of plastic honey bears with various outfits and/or accessories":
Yeah I mean, they are cute little graphics and a fun character/brand, but I don’t exactly see how people consider this some masterful piece of artwork. I don’t live in SF, but I can imagine it gets old to see it everywhere.
The idea that someone is a snob because they dislike generic looking artworks is a hilarious indicator of how far aesthetic discussion and standards have fallen. The word used to mean someone that looks down upon the popular arts in favor of more traditional/expensive/sophisticated art.
Now apparently it means having any standards or metrics of evaluation, period. Either you think everything is equal aesthetically, or you’re a snob.
Thankfully this kind of empty opinion isn’t convincing many people these days.
I’m not “shaming someone’s work,” I said 1) they look like generic graphics, and 2) I primarily said someone isn’t a snob for disliking them, which is what the OP comment claimed.
Even then, analyzing a piece of art work is called art criticism. It’s not exactly a new thing, nor is it some kind of personal attack.
But as I said above, the quality of aesthetic discussion has fallen so much that expressing any critical opinion, no matter how minor, is some kind of shaming attack that indicates I have a personal problem or I’m a snob. Which is a totally insane way to view the world.
Snobbery is a spectrum. You might not perceive your words as snobbery, but I do. We just have a different opinion of where you fall on that snobbery line.
"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
Exactly this. Linker is threading given blocks together with fixups for position-independent code - this can be called rule application. Assembler is pattern matching.
This explanation confused me too:
Each individual iteration: around 4x slower (register spilling)
Cache pressure: around 2-3x additional penalty (instructions do not fit in L1/L2 cache)
Combined over a billion iterations: 158,000x total slowdown
If each iteration is X percent slower, then a billion iterations will also be X percent slower. I wonder what is actually going on.
Claude one-shot a basic x86 assembler + linker for me. Missing lots of instructions, yes, but that is a matter of filling in tables of data mechanically.
Supporting linker scripts is marginally harder, but having manually written compilers before, my experience is the exact opposite of yours.
That's what they said, but as far as I can see it makes no sense at all. It's a console app. It's outputing to stdout, not a GPU buffer.
The whole point of react is to update the real browser DOM (or rather their custom ASCII backend, presumably, in this case) only when the content actually changes. When that happens, surely you'd spurt out some ASCII escape sequences to update the display. You're not constrained to do that in 16ms and you don't have a vsync signal you could synchronise to even if you wanted to. Synchronising to the display is something the tty implementation does. (On a different machine if you're using it over ssh!)
Given their own explanation of react -> ascii -> terminal, I can't see how they could possibly have ended up attempting to render every 16ms and flickering if they don't get it done in time.
I'm genuinely curious if anybody can make this make sense, because based on what I know of react and of graphics programming (which isn't nothing) my immediate reaction to that post was "that's... not how any of this works".
Claude code is written in react and uses Ink for rendering. "Ink provides the same component-based UI building experience that React offers in the browser, but for command-line apps. It uses Yoga to build Flexbox layouts in the terminal,"
I figured they were doing something like Ink, but interesting to know that they're actually using Ink. Do you have any evidence that's the case?
It doesn't answer the question, though. Ink throttles to at most 30fps (not 60 as the 16ms quote would suggest, though the at most is far more important). That's done to prevent it churning out vast amounts of ASCII, preventing issues like [1], not as some sort of display sync behaviour where missing the frame deadline would be expected to cause tearing/jank (let alone flickering).
I don't mean to be combative here. There must be some real explanation for the flickering, and I'm curious to know what it is. Using Ink doesn't, on it's own, explain it AFAICS.
Edit: I do see an issue about flickering on Ink [2]. If that's what's going on, the suggestion in one of the replies to use alternate screen sounds reasonable and nothing to do with having to render in 16ms. There are tons of TUI programs out there that manage to update without flickering.
Great, so probably a pretty straightforward fix, albeit in a dependency. Ink does indeed write ansiEscapes.clearTerminal [1], which does indeed "Clear the whole terminal, including scrollback buffer. (Not just the visible part of it)" [2]. (Edit: even the eraseLines here [4] will cause flicker.)
Using alternate screen might help, and is probably desirable anyway, but really the right approach is not to clear the screen (or erase lines) at all but just write out the lines and put a clear to end-of-line (ansiEscapes.eraseEndLine) at the end of each one, as described in [3]. That should be a pretty simple patch to Ink.
Likening this to a "small game engine" and claiming they need to render in 16ms is pretty funny. Perhaps they'll figure it out when this comment makes it into Claude's training data.
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.
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
> 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
reply