This is getting quite off-topic, but I do love music. At least, that's how I would describe it. I just heard a fragment of something truly beautiful, and the my emotional attachment to that music is quite real (in this case, the Largo of Bach's concerto for two violins, BWV 1043; although I know someone who dismissed it as long-winding).
But words tend to get nerfed, and clickbait culture certainly doesn't help. "Slams" in a headline has been reduced to "made a somewhat negative remark about," and "genius" now means "it took more than 2 seconds of thinking." Let's not discuss what "beyond excited" has become. I too would like word meanings not to shift too fast, as it helps preserve culture, especially literature, but the forces are too strong and diffuse to oppose.
So "I love this web font" now just means "Don't think, just click on this link."
I would love to help bring elegance and beauty to the software we build, both on the inside and outside - and that's my main motivation behind criticising terminals and TUIs specifically.
I have vague ideas for how I could build something ergonomic, easy, and pleasant to use, but I lack experience in this area, and the focus/energy to experiment.
I'm hoping to bring this subject to the light, and have a constructive discussion. If not me, then perhaps someone else will get inspired.
IMO, you need to be a domain expert in order to produce something ergonomic, easy to use. You (or the team you're part of) have to understand the topic and users extremely well. There's no catch-all design, not even a process that covers more than the most mundane cases.
But inspiration is a fickle thing. If you're going to build something, you might as well be inspired by terminal-style interaction, but it can't be the goal.
> If you're going to build something, you might as well be inspired by terminal-style interaction, but it can't be the goal.
100% agree. I believe that if we do replace the terminal, the end result will not be that much different - keyboard first, power users first, APIs that are simple to consume, platform-agnostic. What would make the key differences is letting go of 50 years of accumulated technical debt, that continues to hold back the UX - aka the ergonomics and ease of use.
> IMO, you need to be a domain expert [...]. You (or the team you're part of) have to understand the topic and users extremely well.
"Sometimes Ordis likes to assume he knows nothing. Nobody can learn what they think they already know."
I can’t agree enough. It’s sort of like those massive paintings recreated in CSS. They are a neat achievement, yet sort of reveals a vast emptiness that exists within the author.
reply