5 ms·
Text UIs != Terminal UIs
- lionkor 3y agoI really do like UIs that dump a lot of structured information instead of telling me a shorter but less informative message "for humans". In many cases, I wish UIs in general would be more verbose, utilizing bold text and underlined text to emphasize the most important detail, such as "invalid argument...". I may still want to know which thread, i may want to know its address / tid, I may want to know which scope, which file, the context (caller, callee), etc. I fully get that a lot of interfaces could be more human-friendly, but I'm not sure I would, as a developer building tools for other developers, focus on lower information density.
- diggan 3y agoJust like "security vs convenience", UIs are caught in the middle between two forces pulling them in two different directions. In one direction to provide all the information a power user could use, with dense information and everything available at once, and the other direction being only showing what's absolutely necessary in order to not overwhelm beginners/new users. Lately, a lot of the stuff built towards developers have started to slant in the direction of not being made for power users and only exposing the necessary information, as it seems the new "developer tooling startups" have started to take cues from typical startup product design, for better or worse. It seems to me most products today are not considering which of these directions to aim for, so you get some strange amalgamation between the two where neither groups are happy because it's not right to them, and product owners continue to change the UI to try to make everyone happy, not realizing they end up just serving the lowest common denominator.
- safety1st 3y agoTwo UIs will cost twice as much to design and build, but frankly, we have stdout and stderr today, you just don't see most GUI application developers making use of them. As a developer/power user, if you let me configure your app with a dotfile that I can keep in my git repo, and you spit out useful info via stdout/stderr when I run your app via the terminal... in many use cases I'm happy as a clam to be honest. In fact one reason I tend to gravitate toward open source apps is because they tend to be more likely to do this, what with their users often also being their developers.
- anon373839 3y ago> provide all the information a power user could use > not overwhelm beginners/new users This isn’t the right distinction, IMO. I’m decisively a “power user”, but I hate high-density UI for the same reason I don’t leave all my belongings out in the open: it’s cluttered. Clutter can be stressful and tiring.
- diggan 3y agoYeah, maybe it's not perfect, nor am I saying there aren't exceptions. I guess a good example is Bloomberg Terminal vs whatever investments interface your bank gives you. The latter typically follows the modern design standards of lots of spacing everywhere, using easier to understand terminology and such, while the Bloomberg Terminal is almost straight opposite, cram as much information in as possible, everything available via keyboard shortcuts, industry terms everywhere, favoring quick action and assuming the user mostly knows what they're doing. Both products are built with two different users in mind. I guess the point I was trying to make in the parent comment is that trouble comes when you don't explicitly aim for one of them. Also, clutter/high-density UI isn't the only distinction between the two extremes, also the amount of power the user gets, how many safety features there are, how easy things can be found, how things are explained and more, is also impacted by this.
- Yizahi 3y agoOne important thing to remember - there are power user tools which those user prefer to use and like, and there are power user tools which are simply the only option which is available. A good test may be - can you take a power user tool, slightly but meaningfully improve it and then claim a market share with it? In the case of a Bloomberg terminal- you probably can't, because the value proposition is not the UI or keybinds or actions, but the content and the corporate sources and support behind it.
- anon373839 3y agoYeah, I neglected to mention that there are necessary compromises, and Bloomberg Terminal is a great example. I’m not sure that product could serve its users’ needs without being dense and cluttered.
- Sharlin 3y agoI think people in this discussion are missing the point of the article, which is accessibility, specifically to people using terminals with a screen reader. Visual organization is irrelevant if you can’t see it, and it’s equally irrelevant to the screen reader which just reads aloud all text in the window, expecting something approaching prose rather than {[]}# mess. Sadly I don’t think many authors of CLI software even consider that someone might use their programs with a screen reader, and I don’t think the converse is likely either.
- hliyan 3y agoOn a related note, I wish more ecommerce apps would do english text dumps, rather than fancy 2 dimensional multi-coloured UIs where I need to remember where the date, order number, etc. are. E.g. You ordered a Pepperoni Pizza from Pizza Place for $14.99. Joseph has picked it up. It is due to arrive at your Home (5th Street) at 7.45pm. [Call] or [Message] Joseph. Instead, I get Mission Control.
- qweqwe14 3y agoI'm constantly annoyed by programs that try to make "fancy" terminal UIs, with a ton of formatting, colors, utilizing as many terminal features as they possibly can. It just seems like such a hack to me. The terminal IS NOT meant for fancy user interfaces, stop abusing it for that. Use a real GUI framework that has actual graphics instead of character cells. The question is where to draw the line, I believe things like htop, tmux etc are reasonable, so it's hard to say whether a particular program is "abusing" the terminal.
- ykonstant 3y agoI have the opposite sentiment; I grew up with DOS TUI and miss them dearly. Not all of them were great, but when the programmers focused on the UI experience, you got some really nice results. I do come from a "command line" culture, rather than a "terminal" culture, though; in particular, I don't understand why the command line is "not meant for fancy user interfaces". A "terminal" in the sense of the 60s might, but I don't care about that. I care about the system I have.
- qweqwe14 3y ago> I don't understand why the command line is "not meant for fancy user interfaces" "command line" is a different term from a "terminal", but the reason why it's not great for graphical UIs is that character cells are a bad abstraction for it, people just keep adding more and more features/extensions to terminals to compensate for it, which isn't a good direction at all
- vidarh 3y agoPlenty of fancy user interfaces do not need to be graphical, but can still benefit from better textual presentation. As for "features", there are very few features in modern terminals that affect display that weren't either present in "actual" terminal hardware several decades ago or are spiritual successors to that. E.g. displaying images in terminals has been a thing since at least 1981, yet a whole lot of terminals haven't supported it until it started getting a bit of a resurgence lately. I don't agree it's not a good direction - GUI's are way too complex for a whole lot of applications, where terminals allow you to output quite advanced things with a handful of lines of code and no external dependencies. If there was a push to make GUI protocols simpler (instead of far more work, as with Wayland) for trivial programs to output, I might be more open to this view.
- samsquire 3y agoI actually really enjoy text UIs. I would like something similar to Vimperator or Pentadactyl to label keywords with numbers, perhaps in parentheses or square brackets so I can refer to things without typing them in. This is useful for identifiers which might be uuids, rather than type them in or use the mouse or tmux text selection to select and copy and paste, you can just refer to the numeric identifier. The output for kubectl is text based output table, not a TUI. So it's a really important text format for user interaction. I have had the idea of a text stream format that configures a terminal UI, so it could be used a bit like fzf and selections can be made with arrow keys. In this design, your app would be decoupled from the UI framework (ncurses or Textual, your app is just printf), and you just output a special text format that configures collections which are mapped to portlets in the screen. You can use code similar to what tmux and screen does to arrange the portlets to different parts of the screen.
- auggierose 3y agooverabuse is not really a word
- yellowapple 3y agoEvery English word was at one point not yet a word.
- auggierose 3y agoThat one is never going to be one, as it doesn't make sense. Decide whether you want to say overuse, or abuse.
- kitd 3y agoIf "abuse" means "use badly", it's not too difficult to imagine contexts where "overabuse" makes sense.
- vidarh 3y agoA newspaper archive searchs finds it's been in use since the 1850's at least, and though common it has had brief surges in popularity. To the extent you're "right" that it's not going to be one, it's because its use appears to have faded away in recent years, not because it's not been in use.
- vidarh 3y agoThat should have been "though uncommon"; past the edit window
- xanderlewis 3y agoIf some but not any level of abuse is permissible, then ‘overabuse’ might have some meaning. For example, in mathematical notation this is the case.
- Y-bar 3y ago"Word X is just made up, stop using it!" is an overabused sentiment, one I would say is overabundant among internet pedants. Maybe you are feeling an overwhelming urge to overcorrect grammar? Get over it.
- pgeorgi 3y ago[dead]
- alpaca128 3y agoI'm a bit puzzled by first reading about problems with "graphicality" and "pseudo-graphics frenzy" and then getting an example with no graphics, no ANSI control sequences, no text-based table columns, nothing. The text is more structured than in a novel, but I don't see how that's bad, it seems appropriate for the context even if the screenreader stumbles over it.
- qwerty456127 3y agoNevertheless it probably is much easier (in terms of computational resources needed) to interpret pseudographical picture than to interpret a real graphical picture. This said we probably can put an LLM which would input a pseudographics-rich terminal UI and describe what's there in a meaningful and concise way. I' mot a huge fan of putting an AI into everything but this seems like a natural way to really help disabled people.
- dale_glass 3y agoWhile I sympathize with the needs of accessibility, personally I want to head in the complete opposite direction. Give me a terminal with actual graphics already. Like why is htop drawing stuff with | characters? Use actual pixels, it'll look prettier! We do actually have some capability to do terminal graphics with for instance kitty, but pretty much nothing uses it. But it can be done, example: https://i.imgur.com/fHdkkLn.png https://i.imgur.com/fHdkkLn.png Done smartly, it could actually be more accessible. If we can somehow encode the knowledge "this graphic here is a progress bar at 30%", then we could have much more sensible output on TTS than for "[==== ]"
- silvertaza 3y agoI feel like we're in the extremes in both cases, where general customer interfaces are all super information sparse, and terminals are heavy on text. Having more visual terminals and more text UIs elsewhere would be best of both worlds.
- alpaca128 3y ago> Use actual pixels, it'll look prettier! No, thanks. My problem with such ideas is not the feature itself but the fact that UI tooling always aims to make use of the medium's full potential, and applications then always follow suit. The only reason we don't have animation frameworks for the terminal is because it's not possible, and I'd like it to stay that way. More accessibility would be great but you don't need pixels for that either. Better than images & pixels in the terminal would be a GUI platform that is as simple to use and integrate as the terminal and still feels natural to use with the keyboard. And has a toggle for animations.
- andersa 3y agoWhat do you mean? Animating the terminal is totally possible!
- xg15 3y ago"Better than images & pixels in the terminal would be a GUI platform that is as simple to use and integrate as the terminal and still feels natural to use with the keyboard. And has a toggle for animations." This. What I'd really like is some sort of simple API/structured data standard that tools could implement and then a "generic technical UI" which can automatically generate a UI for that tool. (the UI doesn't have to be pretty or fancy, as long as it lets me quickly and effectively make use of the tools). I think REST endpoints with an OpenAPI definition that automatically lets you generate an HTML documentation with built-in API client goes a bit into that direction. As did Microsoft's idea of "commandlets" I believe. As, actually, did HTML+HTTP in its original inception. However, so far all of those massively fall short in the "allow effective use of the tool" metric: For actual work, it's still way faster and more convenient to make a REST call via curl (once you figured out how to assemble the call!) - than to click around in the OpenAPI client. But maybe some future tool/standard could bring something better to the table here.
- rpigab 3y agoI'm glad the Rust compiler draws ASCII arrows and underlines code elements using the line below, so I'm not sure how an alternative would work there, but IDEs might offer more accessibility around compiler output.
- LoganDark 3y agoWhich one are you calling text and which one terminal?
- augustk 3y agoOberon is another example: https://en.wikipedia.org/wiki/Oberon_(operating_system) https://en.wikipedia.org/wiki/Oberon_(operating_system)
- DinaCoder99 3y agoSurely "espeak" also struggles with the code leading to the debugger, no? This seems like a much larger problem than just the ui, and adding an LLM to the mix isn't going to fix anything. (Unless of course the debugger is being seen by a non-technical end-user, but that again seems like a failure to handle errors in a reasonable way than anything an LLM would solve.)
- deleted 3y ago[deleted]