Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

There’s nothing wrong with that, except it lets ai skeptics feel superior
 help



There are absolutely things wrong with that, because React was designed to solve problems that don't exist in a TUI.

React fixes issues with the DOM being too slow to fully re-render the entire webpage every time a piece of state changes. That doesn't apply in a TUI, you can re-render TUIs faster than the monitor can refresh. There's no need to selectively re-render parts of the UI, you can just re-render the entire thing every time something changes without even stressing out the CPU.

It brings in a bunch of complexity that doesn't solve any real issues beyond the devs being more familiar with React than a TUI library.


It is demonstrably absolutely fine. Sheesh.

It’s fine in the sense that it works, it’s just a really bad look for a company building a tool that’s supposed to write good code because it balloons the resources consumed up to an absurd level.

300MB of RAM for a CLI app that reads files and makes HTTP calls is crazy. A new emacs GUI instance is like 70MB and that’s for an entire text editor with a GUI.


It’s not a bad look at all, no one outside of HN users cares at all

Also some of that ram would be doing other things than the gui…


interesting

I haven't looked at it directly, so I can speak on quality, but it's a pretty weird way to write a terminal app

It’s unusual but it’s a better fit for agentic coding so it makes sense

Oh come on. It's massively wrong. It is always wrong. It's not always wrong enough to be important, but it doesn't stop being wrong

You should elaborate. What are your criteria and why do you think they should matter to actual users?

No, it’s not.

I use AI and I can call AI slop shit if it smells like shit.

And this doesn’t.

It flickers like a mfer.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: