![]() ![]() Re web Vs CLI: I think most browsers have a readability mode or something where you can click a button and just the article body is retained without CSS formatting and stuff. But, you're right about not taking disabilities into account. There are a lot of young folks writing new cli tools in nodejs these days AND thinking about how they can make the visuals more useful to the user. This kind of UI / UX helps avoid bad data entry, mistaken choices, etc. There are SO many opportunities for them to be providing me with useful feedback by leveraging colors, and emoji, and formatting and most of them. As someone who basically lives in the terminal every day I am regularly disappointed by just how poor the current state of cli UI is. I have issues with this general approach to CLI apps. > It's a CLI tool, not a fancy graphical package. The people i see running white terminals almost completely overlap with the people who have done NO customization. ![]() > 1/ if you're running a white (or any other coloured) terminal then odds are you've already changed the other colours to suite (since other applications use the 3/4bit standard as well). ![]() I expect to be proven wrong about the "shouldn't be too hard" shortly. it shouldn't be too hard AND for people without color blindness you could customize the behavior so that it shifted the output of apps like this one to colors more useful / happy-making to you. I can't think of ever having seen an example of this but. modify your shell to run all input through a color shifter. Maybe _that_ is the right solution to the color blindness on the cli. Sure we, as users, can control font choice and size for readability but color? Realistically the only thing i think you could do is install a plugin that compensates for various forms of color blindness by shifting the colors. I can't help but think of what the implications are for them on the web though. Those points are totally valid and really important. eg what if people are dyslexic or partially sighted so have their terminal configured for readability reasons? What the developer is doing is overriding that accessibility setting. > That's another solution but I fundamentally disagree it is a better one. ![]() But I'd honestly rather have developers not using colour at all if they're really that concerned about their output looking identical on every terminal. Unlike many CLI junkies I actually don't mind a bit of colour in the terminal. That's another solution but I fundamentally disagree it is a better one. > A much BETTER solution would be for them to set the background color because they've got a UI specifically designed for dark background. But they are justified in using true colour escape sequences since their entire point is pseudo-graphical. The one exception to this is ASCII / terminal art. You cannot make any assumptions about the terminal eg what if the user has colour disabled entirely - does that then also make the tool "unpredictable"? What about different terminal typefaces? Or widths? You cannot make any assumptions aside that text will be rendered (and even that isn't a guarantee if you're using unicode). It's a CLI tool, not a fancy graphical package. works i guess but it's pretty limiting and only helps people who happened to have completely reworked the definitions of basic things like "white" and "black" and "blue" which would result in a completely unpredictable result for the app creator.ġ/ if you're running a white (or any other coloured) terminal then odds are you've already changed the other colours to suite (since other applications use the 3/4bit standard as well).Ģ/ or if they are just using a preset theme then that theme would have a suitable colour palette alreadyģ/ CLI programs shouldn't be so dependant on the palette of the colours that alternative shades render the tool "unpredictable". If they cannot get the desired effect from that then I'd rather than disabled colour by default and had an optional flag / environmental variable to enable true colour. Using the faint and intense shades for when they need to emphasis stuff. My solution would be to use the standard 8 colour ANSI escapes. ![]()
0 Comments
Leave a Reply. |