things humans are bad at: memorising specific sequences of words
-
english: list files
linux: ls, isn’t that a super clever abbreviation? imagine how much time you’ll save typing it!english: change directory
linux: cd [type the entire name of one of the directories that is literally on the screen right there, you can physically point to it but that will not do anything]some nerd somewhere i am sure: “uhh you can hit the tab key to autocomplete the directory”
me: oh wow it would be super neat if that was written anywhere other than a shitty internet comment about how stupid i am for not knowing that
repeat for every single linux feature
-
things humans are bad at: memorising specific sequences of words
things humans are good at: navigating spaces, finding objects within those spaces, interacting with objects in ways suggested by the object’s appearance and reactions
things linux is good at: making people memorise specific sequences of not quite real words, punctuations, and syntaxes
things linux is bad at: providing humans with coherent, consistent and stable spaces to navigate, or objects with appearances or reactions that suggest their function
@bri7 at this point i just hate software
so many potentially good ideas. nearly no good and complete implementation
-
things humans are bad at: memorising specific sequences of words
things humans are good at: navigating spaces, finding objects within those spaces, interacting with objects in ways suggested by the object’s appearance and reactions
things linux is good at: making people memorise specific sequences of not quite real words, punctuations, and syntaxes
things linux is bad at: providing humans with coherent, consistent and stable spaces to navigate, or objects with appearances or reactions that suggest their function
@bri7
Ugh. Give me spacial metaphors any day.iirc, some Lisp Machines let you click on directories to switch to them so it's not a new idea.
-
some nerd somewhere i am sure: “uhh you can hit the tab key to autocomplete the directory”
me: oh wow it would be super neat if that was written anywhere other than a shitty internet comment about how stupid i am for not knowing that
repeat for every single linux feature
@bri7 A lot of Linux was styled after older, similarly obtuse systems that had to be a little curt with i/o because they ran on mainframes built when 4kb was a lot of memory.
Only nerd nostalgia keeps it that way. While some attempts have been made to improve the situation, like the fish shell, none of them go far enough.
-
@bri7 A lot of Linux was styled after older, similarly obtuse systems that had to be a little curt with i/o because they ran on mainframes built when 4kb was a lot of memory.
Only nerd nostalgia keeps it that way. While some attempts have been made to improve the situation, like the fish shell, none of them go far enough.
@bri7 The nerd in me would use the 'alias' command to redefine commands until it made sense to you (like "alias list=ls" to tell the computer "hey, when she types list, she really means ls, okay?)
The ux engineer in me would just install the x11 graphics system, use the Slackware "hotdog" project to make it look exactly one a computer system you used before, install the pcmanfm file manager and make it's menu option called "file manager" -
undefined oblomov@sociale.network shared this topic
-
things humans are bad at: memorising specific sequences of words
things humans are good at: navigating spaces, finding objects within those spaces, interacting with objects in ways suggested by the object’s appearance and reactions
things linux is good at: making people memorise specific sequences of not quite real words, punctuations, and syntaxes
things linux is bad at: providing humans with coherent, consistent and stable spaces to navigate, or objects with appearances or reactions that suggest their function
@bri7 isn't this a command line issue in general?
-
@bri7 isn't this a command line issue in general?
@oblomov it is extremely possible to make a command line system that does not require people to memorise exact sequences of words. the popularity of search engines and chat GPT are two visible examples
-
@oblomov it is extremely possible to make a command line system that does not require people to memorise exact sequences of words. the popularity of search engines and chat GPT are two visible examples
@bri7 I wouldn't define those as command line systems, TBH.
-
@bri7 I wouldn't define those as command line systems, TBH.
@oblomov well, then you’d be wrong
-
things humans are bad at: memorising specific sequences of words
things humans are good at: navigating spaces, finding objects within those spaces, interacting with objects in ways suggested by the object’s appearance and reactions
things linux is good at: making people memorise specific sequences of not quite real words, punctuations, and syntaxes
things linux is bad at: providing humans with coherent, consistent and stable spaces to navigate, or objects with appearances or reactions that suggest their function
@bri7 In other words, Emacs > POSIX. -
@bri7
Ugh. Give me spacial metaphors any day.iirc, some Lisp Machines let you click on directories to switch to them so it's not a new idea.
@bri7
Oh, the last time I played with the Inspector in McClim it also allowed you do to this and more.
May be worth a look for anyone interested in this. -
some nerd somewhere i am sure: “uhh you can hit the tab key to autocomplete the directory”
me: oh wow it would be super neat if that was written anywhere other than a shitty internet comment about how stupid i am for not knowing that
repeat for every single linux feature
@bri7@social.treehouse.systems
oh wow it would be super neat if that was written anywhere other than a shitty internet comment about how stupid i am for not knowing that
In Bash's manpage it's written in the §Readline - Completing.
Completing complete (TAB) Attempt to perform completion on the text before point. Bash at‐ tempts completion treating the text as a variable (if the text begins with $), username (if the text begins with ~), hostname (if the text begins with @), or command (including aliases and functions) in turn. If none of these produces a match, filename completion is attempted.Granted it would've been helpful if there was some built-in tutorial feature.
Part of the issue here is that POSIX & UNIX expect you to have a physical user manual or guidebook/handbook or to already be familiar with UNIX & POSIX.
Because historically it was easier and cheaper to have a paper book available (things have certainly changed).
-
@bri7 A lot of Linux was styled after older, similarly obtuse systems that had to be a little curt with i/o because they ran on mainframes built when 4kb was a lot of memory.
Only nerd nostalgia keeps it that way. While some attempts have been made to improve the situation, like the fish shell, none of them go far enough.
@madengineering @bri7 > Only nerd nostalgia keeps it that way.
Some things are required to be crappy by POSIX.
Shells that do structured pipes are incompatible. -
@bri7 I wouldn't define those as command line systems, TBH.