What bothers me is that the maintainer quoted at the beginning of the piece is holding this up as almost a virtue: look at this complex thing we've done! But... at its core it's a TUI rendered perhaps what is the most complex and least efficient way possible.

I'm not part of a hypergrowth LLM company, but I do wonder why someone there would take such pride in such inefficient choices.

And as someone who's been using TUIs for ... more years than I'd care to admit ... it's not a particulalry stunning example of one either. I like it fine. It mostly does the job. But it's pretty simple as TUIs go and I could think of ways it could be better.

CC has a complex scene rendering pipeline with a 16ms/frame budget. That is much closer to a game engine than a print statement.

I've only been using it for a month, but it quickly becomes incredibly laggy. I have to kill it completely and reopen it[1]. I've also had some unique hard locks never before seen on my machine[2], only while it's open and doing things.

I also haven't noticed it outputting anything that would warrant it being more complex than ncurses or the current fashionable equivalent?

[1] /clear helps but not 100%, and the time to get back to lag land increases each time

[2] (Framework 13" AMD 7840U 32GB RAM)

this statement is ridiculous and stinks of AI bro superiority