We replaced H.264 streaming with JPEG screenshots (and it worked better)

Post by Anamon » Sat, Dec 27, 2025, 10:35 AM UTC

tomjakubowski wrote: post #330

throw-12-16 wrote: post #298

Earlier quoted context omitted.

How many people do you know that use em dashes —- none.

Em-dash has a trivial and mnemonic shortcut on Macs (Option-shift-hyphen), so I've been an em-dash user for as long as I've had one.

I committed typing en-dashes and ellipses on Windows to muscle memory. Alt+0150, Alt+0133. Bam!

I'm sure there are easier ways this can be set up. But, as I said, muscle memory.

Although I'll have to admit that wanting to use proper typography in the first place probably started when I was typesetting a print magazine on a Mac, where it's super easy to do it the proper way.

(I'm also never going to let AI slop discourage me from trying to use proper punctuation.)

Post by Anamon » Sat, Dec 27, 2025, 11:11 AM UTC

imiric wrote: post #187

> By the time you see a bug, the AI has already committed it to main If you have given your "AI" full control over your repo so that it can commit unreviewed code to the main branch, you have far greater problems than a 45 second video stream delay. Besides, you'd need superhuman abilities to spot a bug in hundreds of lines of generated code in under 45 seconds. I know this example is rhetorical and likely produced b…

Yeah, that was my main head-shaking moment in that entire piece as well.

Tell me again about these grandiose efficiency gains from agentic coding assistants, which I'm apparently supposed to supervise in real time as they produce shittier code than I would've. And about what an excellent idea it is to have software developed this way by people who don't understand why an automated system being able to commit to a main branch might be problematic.

Re: We replaced H.264 streaming with JPEG screenshots (and it worked better)

Re: We replaced H.264 streaming with JPEG screenshots (and it worked better)