John Siracusa

And your point about thin clients is true.

Although I did see a thread recently of someone describing how the Claude terminal command line application works and showing the usage, the, the, um,

the resource usage of it.

In theory, there's no reason that a thin client that uses a terminal input that just as a text, you know, curses style text display, that should be able to be incredibly thin.

Cause it's just like, I send texts to the server, I get texts back.

If the server's doing all the work, I should be both fast and low resource usage.

But the stats they showed were not low because they had found this very convoluted way to do a command line application.

No, they're not using the... Well, maybe they are using the Curses library, but they're running a React app behind the scene and rendering to a 2D backing buffer and pixel diffing it and then sending terminal escape sequences to...

Anyway, the point is they were showing like gigs of memory usage for what is essentially a Node.js app or whatever language it's written in that just sends HTTP requests to a server and gets responses and spits them.

We've all used it.

It's a text.

It's a terminal application.

It is not a GUI.

And yet it uses huge resources.

So while in theory and technically you are correct, I'm not sure current software practices are taking full advantage of the thinness of the client right now.

Yeah, they're not using coding agents or whatever.

But the command line, cloud executable or code executable does.

One more thing.

Um,

So this is also a cost saving thing, obviously, because, you know, everything is about cost saving with this thing.