Hacker News Reader

Comment by piskov | Hacker News Reader

Thank god it’s not another React, Solid, Typescript, what have you, web abomination inside the terminal (claude code, opencode, I’m looking at you).

Bravo!

View on HN

> claude code, opencode, I’m looking at you

Could you elaborate? I mean, I get the usual criticism of web/Electron-based desktop applications (slow, includes a whole Chrome engine, non-native UI, …) but Claude Code isn't one of them?

Search for twitter drama where Anthropic engineer says basically the following [1] and gets shamed by what AAA game developers are able to render at the same time.

tldr; the ui you see in the terminal is react-based in claude code. As for opencode just see their repo on github.

[1] https://news.ycombinator.com/item?id=46706040

That's where codex-cli shines (rust)

the startup time is crazy, you can start writing as soon as you hit the command

(I don't use codex, just noticed that it's crazy fast)

Sadly the fast startup time is overshadowed by the slow response time of the codex agent

I don't get it. Even in ChatGPT I always use Pro model with maxed-out thinking budget (selectors available only on web and windows).

Let them cook as much as they can.

Looks like there're two main approaches to AI-first development: (i) favor slow responses to produce an upfront high-quality result, (ii) favor quick responses to enable faster response-test-query iteration. And, based on comments read here, seems Codex isn't too fit for the later. Optimally a developer should be able switch between the two approaches depending on problem at hand.

Reply on news.ycombinator.com