logoalt Hacker News

GreenSalemyesterday at 7:22 AM5 repliesview on HN

Incoherent and far too long .

Lists a bunch of things .

Fails to make any clear points .

Fails to give real reasons for the few claims it makes .


Replies

joshkayesterday at 5:01 PM

I really liked this article (despite disagreeing with its conclusion and agreeing with many of the concerns about failures of TUIs). It gave a feeling of "here's a bunch of cool stuff I've done" to help back the claim, which is far more personal than a lot of blog posts tend to be.

show 1 reply
PaulRobinsonyesterday at 7:43 AM

Building software for yourself - and only yourself - is a super-power.

I can see how LLMs help.

I wouldn't want to maintain software for other people entirely vibe coded. I think I might think again about native app development for my own needs, if it's kind of disposable.

zombotyesterday at 11:07 AM

But it makes some things very clear:

- All those GUI windows look the same. How the fuck do I tell one app from the other?

- The abysmal corner radii are a clear indication of terminal macOS. Pun fully intended.

dmos62yesterday at 7:50 AM

Spent 2 minutes skimming, didn't manage to find a single talking point. I've no idea what the thesis is. Seemed like a list of things this person built.

People talk shit about LLM writing. Well, here's a prime example of why I like LLM-speak. Does this article have personality? Yes. Attitude? Yes. Is it structured and accessible? No.

I'll take clarity over personality any day of the week.

show 1 reply
mike_hearnyesterday at 9:10 AM

Did you read it all the way to the end? It's coherent and does give real if debatable reasons for the claims it makes, I think it also does so quite clearly although if I'd written it the ordering of the sections would be different.

Here's an organically grown summary:

• TUIs suck because they are primitive, often buggy, hard to write and aren't accessible. Their existence isn't due to any real technical advantage but more because UNIX historically had a very bad UI toolkit (Motif) which established a 'culture' of TUIs.

• It's now easy (on macOS) to write native apps that use SwiftUI and give a much better GUI. You can just vibe code them.

• Some specific skills, features, templates etc are linked which look useful if you agree with this approach.

• You don't have to give up remote access because there's no reason the GUI has to run on the same machine as the thing it controls. A native GUI can just SSH in to a remote machine and run non-TUI CLI tools to control it. Lots of apps have worked this way and it functions fine.

• On the other hand, TUIs are portable (ish). The author concedes this may sometimes be useful.

show 1 reply