My proposal would be to define a set of intents for 0-15 with sensible defaults and let terminal themes assign any color they would like to those. 0 would be background, 7 for foreground , 1 for highlight, 3 for titles, 4 for frames and from there work on backgrounds also..
We should define a set of base colors for terminal apps that are used for themes so that we have a common set of colors for all term apps.
Text, background, borders, hilight, muted then let the terminal set its theme.
Infortunately, this is where free market stops being a good optimizer and manual settings (laws) need to apply by requiring raiparability, which is difficult (but not completely impossible) to quantify.
You're right of course but it also depends on how long you want to spend on it. If Python gives you radix sort directly and the C implementation you can have with the same time is bubble sort because you spent much time setting up the project and finding the right libs it kinda makes sense.
I really think we should converge to semantic codes. By example Background is zero, standard is 7, positive / negative, highlight, colored1,2,3 .. with correct defaults, and let the user have a common 8 or 16 colors palette in the terminal for all textmode apps. Imagine having some kind of unified color themes in the terminal.
Emojis aren't 7-bit clean. They're hard to type. They don't mean things the same way words do. `foo | grep -i error` communicates intent better than `foo | grep :-/` or whatever goofy hieroglyph someone chose instead of, like, a word with clearly defined meaning.
In my experience with live codebases, "error" or "warning" rarely mean the same thing to the same person, but admittedly you're much more likely to guess that they're in use as opposed to crying-green-clown emoji
I'd like to recommend rofimoji. I have it bound to a hotkey, so whenever I want to type an emoji, I just hit that hotkey and then a window pops up with my most recent emoji already visible at the top. Then I start typing in words that describe the emoji that I want like "crying" and it filters the list. Finally I select one and it pastes it into whatever text box I had selected before I hit the hotkey. My only complaint is I wish it worked for all unicode codepoints instead of just the emoji.
Yes that's why I also mentioned text labels. (strikethrough ansi codes aren't also fun to type). Besides, where are you needing 7but clean data ? Isn't that a narrow use case ?
It's the robustness principle. "Be conservative in what you do, be liberal in what you accept from others." A CLI author shouldn't assume support for UTF-8.
ok in that context use error or ok, just dont use color as ~10% of ppl have an issue with seeing colors perfectly (that includes people with epaper displays)
That depends on too many factors. Moving all production to the US would greatly reduce prices, since it costs a lot of money to setup a factory, but you amortize that over everything it produces. I don't know how the iphone is produced in China, but I have to believe it is highly automated as well. However moving a factory takes months (at best, China may not allow exporting it at all), and in those months Apply wouldn't be making any iphones, so to do production in the US requires building an all new factory which is going to be expensive.
You can buy modern CPUs made in Iowa - at about $60,000 each. You can buy one from an intel fab (I'm not sure where they are) for under $1000 that is likely better. the Iowa made CPU would be a one-off made under license from Intel. The companies that do this made just enough to prove they can in case Intel fabs are bombed. (I assume this means that you can't actually buy such a CPU if you tried, but they do make them and that is about the cost they would have to charge to break even)
reply