TVs are NOT powerful. It’s like writing software for the Lunar rover.

Even the slower ones are more like a Wii U, which is perfectly capable of everything a set-top box needs to do. Really, the hardware acceleration does all of the heavy lifting, and the processor only needs to render text and coordinate what to composite.

It's the bloat of the software layer on top that's slowing things down.

A 1st-generation Chromecast only has 512 MB pf RAM and a dual-core 1.2 GHz processor, and it can handle video streaming just fine. Building an interface on top of that doesn't take a lot of resources, if the underlying layers aren't bloated. With current Android/iOS development, they very much are.

Yes this is a waste of time. It’s actually a hard engineering problem! There are very few engineers who build for TV compared to desktop or mobile. The challenges are totally different. There are still some good human-written articles out there.

This is basically what Dreaming Spanish does right? Just shit loads of comprehensible input videos.

This is actually embarrassing. His "radically different" workflow is... using the built-in Plan mode that they recommend you use? What?

It's not, to be fair.

> I use my own `.md` plan files rather than Claude Code’s built-in plan mode. The built-in plan mode sucks.

From Claude docs: Planning is most useful when you’re uncertain about the approach, when the change modifies multiple files, or when you’re unfamiliar with the code being modified. If this isn't true, skip the plan.

Can you easily version their plans using git?

"Write plan to the plans folder in the project"

Can that be saved somewhere so it's done for every session?

You can just read the docs man

Docs are offline? Has this shut down already??

We have to start banning users who do this

Just use Drizzle

That’s what I thought.

The queries look a but more clumsy then but you won’t cause problems when spelling the column names.

  const [domain] = await db
    .select()
    .from(cmsDomains)
    .where(eq(cmsDomains.id, domainId))
    .limit(1);

Please tell us why we should.

Because it's a solved problem

That sounds weird. Why does it need a video feed? The computer can already generate an accessibility tree, same as Playwright uses it for webpages.

So that it can utilize gui and interfaces designed for humans. Think of video editing program for example.

Yes. GUIs expose an accessibility tree.

Even if they do (often not the case) this will be far from exhaustive, and likely won’t reflect the structure of the application very well. Vision based testing is often combined with accessibility based testing

Not all of them do, and not all of the ones that do expose enough to be useful to the AI.

I feel like a legion of blind computer users could attest to how bad accessibility is online. If you added AI Agents to the users of accessibility features you might even see a purposeful regression in the space.

No because this was not a billion dollar business

I mean, the cascade really doesn't suck though does it. You really want to set font families and sizes on every p tag?