Hacker News Reader

Comment by nasso_dev | Hacker News Reader

shouldn't we focus on human accessibility first? it also makes things more "machine accessible" as a byproduct, but at least humans remain the main focus

also, openshot is foss. can't you just give the source code to your clanker and let it mod itself in the app?

View on HN

> shouldn't we focus on human accessibility first?

This is the big question for designers, how much of the future of software will be human-oriented UIs vs a human typing into a chat window (or as a temporary bridge, telling an agent to operate existing GUIs).

For now I believe agent-driven software is still pretty niche, something for highly technical users, but that will change as it mainstreams. Early adopters demand early adopter software features.

a chat window is actually HORRIBLE for many tasks. i really strongly hope this isn't what the future of software looks like

there is just no way a chat interface could replace a non-linear video editor gui

I would assume it would be for driving via agentic means, more AI video slop.

> a chat window is actually HORRIBLE for many tasks. i really strongly hope this isn't what the future of software looks like

I strongly concur - I don't want to "tell" the app to level the audio between several clips only to have it level everything to 0 and then take five minutes to undo etc

Everyone always views it through the current UX when I say stuff like this. The way I see it is we're in the DOS/UNIX era of LLMs where you're just staring at an empty text input box, it's slow, breaks often, GUI integrations are non-existent or primitive, etc.

It's not a replacement for sure. There's no way it could be a full replacement for visual UIs.

Yes we should. Still UI is for telling the software to do meaningful work. Which means that every well designed UI software will have ready to expose api lurking just benath the surface.

Of course the human UI should be first. Did anyone say anything different?

Reply on news.ycombinator.com