bla3

It's alright.

This sounds roughly right to me, except for "maintainability". In my experience, agents really don't like deleting code unless you explicitly ask for it. If you're not careful, you end up with new better implementations of things but with the old implementation still around in perpetuity. Humans do this too of course.

If you're reading this and you're put off by the "uses an LLM", don't be. This is not a low-effort video, quite the opposite. This is one of the best YouTube videos I have ever seen.

Mirrors my experience: LLMs are really good at optimizing, better than most humans. But also, they tend to not reach absolute peak performance where people made an effort to optimize something.

Since most problems see fairly little optimization, that's still a big win most of the time.

> 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.

This is the mindset that gives you Java-Style GUIs.

I love the recently added "In Response to Hacker News" section.

> "can't make 9 babies in a month"

It's "9 women can't make a baby in one month".

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.

Since then, Swift also grew excellent C++ interop, something Rust doesn't have at all.

It's a shame that JpegXL doesn't have a freely available spec.

If they use Rust for new code and C++ changes are all in old code, this could be explained just by older code being more risky to change.

There was a ton of backlash when Glass launched. Search for "glassholes" to find articles on that topic from back then.