But why do we care about graphics in a terminal? If I want to display graphics, I'll use a GUI, if I don't care, I'll use a terminal.
If I want to use graphics remotely, there's X, or any number of remote desktop solutions, or scripting remote data and local programs, or web browsers.
Last response because you clearly didn't read my first comment or any of my others.
> None of those things are true, though. You can have all of those exactly like before. But you can now also do, for instance, "cat image.jpg" and you will see the image inline in your terminal. That only adds value and prevents nothing
That case is covered by Sixel [0] like I mentioned before.
Also, the use for 'cat' is not to display the contents of a file, but to output the contents of a file for concatination, so 'cat image.jpg' doesn't make sense.
> Again, I specifically said I do not want a GUI
This is also not what you said before when you said
> And there are plenty of CLIs that use graphics. Just not for controlling computers for some absurd reason.
You know what something that uses graphics to control computers is? A user interface, with graphics... I wonder if there's an acronym for that. The fact that graphics are a key part of usage make it a GUI by default.
But why do we care about graphics in a terminal? If I want to display graphics, I'll use a GUI, if I don't care, I'll use a terminal.
If I want to use graphics remotely, there's X, or any number of remote desktop solutions, or scripting remote data and local programs, or web browsers.