Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

The Codex App

openai.com

Post reply on HN
Print view View original

341–350 of 671 posts

Re: The Codex App

#341

Post by luckman212 »

jarek-foksa wrote: post #282
OlympicMarmoto wrote: post #265

Earlier quoted context omitted.

This is another common excuse. You don't need to use microsoft's or apple's or google's shit UI frameworks. E.g. see https://filepilot.tech/ You can just write all the rendering yourself using metal/gl/dx. if you didn't want to write the rendering yourself there are plenty of libraries like skia, flutter's renderer, nanovg, etc

Customers simply don't care. I don't recall a single complain about RAM or disk usage of my Electron-based app to be reported in the past 10 years. You will be outcompeted if you waste your time reinventing the wheel and optimizing for stuff that doesn't matter. There is some market for highly optimized apps like e.g. Sublime Text, but you can clearly see that the companies behind them are struggling.

> Customers simply don't care. I don't recall a single complain about microplastics in the past 10 years.

> You will be outcompeted if you waste your time reinventing the wheel and optimizing for stuff that doesn't matter. There is some market for safe, environmentally-friendly products, but you can clearly see that the companies that make them are struggling.

ok.

Re: The Codex App

#342

Post by energy123 »

dworks wrote: post #321

Somewhat underwhelmed. I consider agents to be a sidetrack. The key insight from the Recursive Language Models paper is that requirements, implementation plans, and other types of core information should not be part of context but exist as immutable objects that can be referenced as a source of truth. In practice this just means creating an .md file per stage (spec, analysis, implementation plan, implementation summa…

This is what I've been doing. Iterating on specs is better than iterating on code. More token efficient and easier to review. Good code effortlessly follows from good specs. It's also a good way to stop the code turning into quicksand (aside from constraining the code with e2e tests, CLI shape, etc).

But what is your concept of "stages"? For me, the spec files are a MECE decomposition, each file is responsible for its unique silo (one file owns repo layout, etc), with cross references between them if needed to eliminate redundancy. There's no hierarchy between them. But I'm open to new approaches.

Re: The Codex App

#343

Post by karmasimida »

tartoran wrote: post #268
karmasimida wrote: post #181

Not to rain on the parade, but this app feels to me ... unpolished. Some of the options in the demo feels less thought out and just put together. I will try it out, but is this just me, or product/UX side of recent OpenAI products are sort of ... skipped over? It is good that agents help ship software quickly, but please no half-baked stuff like Altas 2.0 again ...

What else do you expect from vibecoding? Even the announcement for this app is LLM generated.

This is true. The font and animation feels basic to me, even as a programmer focused app

Re: The Codex App

#344

Post by marxisttemp »

jarek-foksa wrote: post #282
OlympicMarmoto wrote: post #265

Earlier quoted context omitted.

This is another common excuse. You don't need to use microsoft's or apple's or google's shit UI frameworks. E.g. see https://filepilot.tech/ You can just write all the rendering yourself using metal/gl/dx. if you didn't want to write the rendering yourself there are plenty of libraries like skia, flutter's renderer, nanovg, etc

Customers simply don't care. I don't recall a single complain about RAM or disk usage of my Electron-based app to be reported in the past 10 years. You will be outcompeted if you waste your time reinventing the wheel and optimizing for stuff that doesn't matter. There is some market for highly optimized apps like e.g. Sublime Text, but you can clearly see that the companies behind them are struggling.

I care. I refuse to use Electron slop unless it is literally the only option available (usually due to some proprietary locked-in platform eg Discord). I will happily pay significant sums of money for well-made native apps that often have fewer features than the Electron versions, simply for the pleasure of using tools that integrate seamlessly with my operating system. Not all of us have given up on software quality.

Re: The Codex App

#345

Post by marxisttemp »

belfthrow wrote: post #310
zem wrote: post #305

Earlier quoted context omitted.

"native" is used for different things, from "use the platform's default gui toolkit" to "compile to a machine code binary". the former is a bit of a mess, but the latter is strictly better than wrapping a web view and shipping an entire chrome fork to display and interpret it. just write something in qt and forget about native look and feel, and the performance gain will be enough to greatly improve the user experien…

Should just use javafx or swing. Take a leaf out of intellij which while it as it's own performance problems (although not from the fact of the ui framework) has a fantastic ui across Mac / windows / nix

Non-native UI widgets, non-native runtime, non-native language

Re: The Codex App

#346

Post by tonkinai »

romainhuet wrote: post #62
vzaliva wrote: post #28

How about us, Linux users? This is Mac only. Do they plan to support CLI version with all the features they are adding to desktop app?

Hi! Romain here, I work at OpenAI. The team actually built the Codex app in Electron so we can support both Windows and Linux very soon. Stay tuned!

Do you plan to release a build for Mac Intel?

Re: The Codex App

#347

Post by marxisttemp »

romainhuet wrote: post #294
measurablefunc wrote: post #248

Earlier quoted context omitted.

Their goal is to ship as fast as possible b/c they don't care about what you care about. Their objective is to gather as much data as possible & electron is good enough for that.

I work at OpenAI, and I get the concern. From our side, this was a careful tradeoff: Electron lets us iterate faster and makes it possible to bring the Codex app to Windows and Linux very soon. That doesn’t mean performance or UX don’t matter—we’re actively paying attention to both. Would genuinely love your thoughts if you try it. Early users have been surprised by how native it feels!

Your AI can’t make a UI for 3 platforms? Seems pretty worthless.

Re: The Codex App

#348

Post by marxisttemp »

wilg wrote: post #290
OlympicMarmoto wrote: post #220

It is baffling how these AI companies, with billions of dollars, cannot build native applications, even with the help of AI. From a UI perspective, these are mostly just chat apps, which are not particularly difficult to code from scratch. Before the usual excuses come about how it is impossible to build a custom UI, consider software that is orders of magnitude more complex, such as raddbg, 10x, Superluminal, Blende…

Unpopular opinion: why would you want a "native app"? On macOS, basically every app Apple makes themselves is worse in terms of design, usability, and performance than a popular Electron-based alternative. For example, I tried opening a 200MB log file in Apple's Console.app and it hung. Opened right up in VS Code.

What is the superior Electron based alternative to Pixelmator Pro? Final Cut? Logic? Pages?

Re: The Codex App

#349

Post by autoconfig »

OlympicMarmoto wrote: post #220

It is baffling how these AI companies, with billions of dollars, cannot build native applications, even with the help of AI. From a UI perspective, these are mostly just chat apps, which are not particularly difficult to code from scratch. Before the usual excuses come about how it is impossible to build a custom UI, consider software that is orders of magnitude more complex, such as raddbg, 10x, Superluminal, Blende…

> This requires calling native APIs (e.g., Win32), which is not feasible from Electron.

That is not correct. One of the major selling points of Electron is precisely that you can call native APIs.

Re: The Codex App

#350

Post by fnord77 »

belfthrow wrote: post #310
zem wrote: post #305

Earlier quoted context omitted.

"native" is used for different things, from "use the platform's default gui toolkit" to "compile to a machine code binary". the former is a bit of a mess, but the latter is strictly better than wrapping a web view and shipping an entire chrome fork to display and interpret it. just write something in qt and forget about native look and feel, and the performance gain will be enough to greatly improve the user experien…

Should just use javafx or swing. Take a leaf out of intellij which while it as it's own performance problems (although not from the fact of the ui framework) has a fantastic ui across Mac / windows / nix

Java swing is way underrated despite being very complex. It baffles me why this just sort of withered on the vine.

(I was a swing developer for several years)

Post reply on HN