News for hackers. Stuff that matters.
Re:Telling a Computer to Do Things by kalx on Sunday September 20, 2026 @06:15AM (#49774366)
But you’re still limited by the designer of that shell? Or userspace? Or kernel? Or cpu architecture? I mean, how deep should you go before «it’s however YOU want»?
Re:Telling a Computer to Do Things by ryuuseijin on Sunday September 20, 2026 @06:39AM (#49774469)
There are some really powerful UIs that are extremely flexible, like spreadsheets, or ComfyUI, or certain issue trackers. On the whole however I would say they all still are mostly their own interaction silos and integrations with other programs have to be explicitly built for each app.

The great thing about a shell is that you can glue together programs that don't know about each other. This is not a silver bullet, with shell programs being text oriented etc., but it does give rise to some powerful possibilities that don't really work with UIs.

Re:Telling a Computer to Do Things by sire-vc on Sunday September 20, 2026 @09:19AM (#49775577)
This is the exact problem with the Unix greybeards smug nature: no matter how low level you go you are always on top of some abstractions.

Criticising people just because they don't use your choice of tools is just elitism and leaves a bad taste.

If someone uses a GUI to accomplish their goals that should be complimented not criticised.

Re:Telling a Computer to Do Things by ZeroDayDreamer on Thursday September 24, 2026 @07:08AM (#49828972)
Sure, and at some point you're limited by physics. But "limited by the universe" and "limited by what a product manager imagined in 2019" are pretty different kinds of limits