> I built one, by porting Boehm’s engine.
> It’s 2026, so I didn’t hand-write the port. I directed Opus 4.8 to translate the source line by line into Swift
I wish I could filter out stuff like this. Cool work by Hans Boehm, but what's the value add in this blog post.
I like to think everyone came to the conclusion that it would strengthen the piece if most comments on it appear to miss the point and are slightly robotic.
Why do Hunyuan, OpenAI 4o and Gwen get a pass for the octopus test? They don't cover "each tentacle", just some. And midjourney covers 9 of 8 arms with sock puppets.
I think that might be true of the language committee, but there's presumably a huge crowd of people with existing c++ code bases that would like to have a different path forward than just hoping that the committee changes priorities.
WebP lossless is close to state of the art and widely available. It's also not widely used. The takeaway seems to be that absolute best performance for lossless compression isn't that important, or at least it won't get you widely adopted.
That's a critique of `async`, not of `using` though, right? This doesn't seem to make functions more colored than they already are as far as I understand.
In my experience they're not great with mathy code for example. I had a function that did subdivision of certain splines and had some of the coefficients wrong. I pasted my function into these reasoning models and asked "does this look right?" and they all had a whole bunch of math formulas in their reasoning and said "this is correct" (which it wasn't).
I wish I could filter out stuff like this. Cool work by Hans Boehm, but what's the value add in this blog post.