![]() ![]() It has coincided with the creation of a lot of new terminal emulators (some of the youngest have the most support for sixel and similar features), and with the trend of using GPU acceleration in terminal emulators. Yep! It's surprising to me, too, how recently (within the past 4 years, by my estimation) there has been an intense, renewed interest in sixel. Doing it on anything else (Python, C, whatever) requires more code. ![]() Right now, the easiest and quickest way to make ad-hoc arbitrary arrangements of file descriptors is with the shell's file redirection features. Processes will have inheritable file descriptors. What's a better alternative? To just remove file redirection features and leave piping? Arrow from file to command for input, arrow from command to file for output. That said, the redirection operators seem as intuitive as they can be. Many things imply trade-offs, and for example if the average potential user values versatility over intuitiveness, and there's a tradeoff to be made between the 2, it's ok to not go for the intuitive option. ![]() I don't think being intuitive is always the most important criteria to something being well designed. > Maybe the way shell handles input, output, and redirection isn't intuitive and poorly designed. That is, most learners of the shell before were probably motivated to use it as their main interface, later one of their main interfaces, and now maybe there's a lot of people that need to run a command or 2 but don't really want to use it as an interface at all, so they never bother to learn beyond the most absolute minimum they need to. What's probably going on is that the boundary between basic and intermediate probably moves depending on increased adoption with different proportions of motivations. I don't mean in our circles, but in general. I feel that's the same bar as saying that knowing how to use a keyboard and mouse is not basic because most people just learn to use their phone's touch interface, given how there's now a lot of people that have a smartphone but not a computer. I'd say "basic" shell knowledge is that commands or programs produce output which is where many stop and why it's common to use cat this way. I'm pretty sure anyone that points out ` There is room for other interpretations, but I'd say if it's super common for people to not know something, which appears to describe this, it doesn't meet the definition of basic. > In general I tend to err less on the side of "you're holding it wrong" gatekeeping in tech The tradeoff between readability and performance is always a case-by-case decision. ![]() To someone who's fully internalized the workings of the shell, then sure, using `you can have the inputfile precede the process, but then you have to precede _that_ with a glyph which appears to suggest "send this data to the preceding command". > looks somehow, as if there were an arrow pointing to the left, where nothing is. > has to jump over process1, and then read left to right. > `cat infile | process1 | process2 > outfile` > We are used to read from left to right, so a command like Sure, and as another answerer of that SO question points out: ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |