Re:The Codex App
by zem on Monday February 02, 2026 @06:23PM
(#46863701)
"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 experience.
[ Parent
| on HN ]
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
I can’t tell if this word salad is sarcasm or genuine.
From the suggestions it looks like sarcasm, but you never can tell these days
Re:The Codex App
by marxisttemp on Monday February 02, 2026 @08:31PM
(#46865097)
Non-native UI widgets, non-native runtime, non-native language
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)
The web sucked all the oxygen out of the room.
Re:The Codex App
by pregnenolone on Tuesday February 03, 2026 @04:31AM
(#46868692)
It really was Oracle’s fault – they neglected deployment for too long. Deploying Java applications was simply too painful, and neither JLink nor JPackage existed.