61–70 of 79 posts
I love my dependence on the GUI, otherwise would still be stuck using MS-DOS.
If MS-DOS had enjoyed as much developer attention as the *nix command line experience has over the past couple of decades, that might not be so bad a prospect.
This article is awful. You're not going to "break your dependence on the GUI" by replacing 5 things you do a few times a day with obscure, less good CLI alternatives. What about things like manipulating files and running programs? Aren't they the things people do with computers? Also, bc is especially terrible. Nobody who is already "dependent on the GUI" is going to want to know about scale= and all that. Better to…
I'm a little late to the party, but something I've come realize recently is that my affection towards CLI applications comes from the fact that I usually don't have to take my hands off the keyboard. Human hands can move very fast, faster than we can assemble cogent thoughts thanks to muscle memory (and other things that I'm sure I'm not aware of). I don't know if this is a universal thing, but I like it when I don't…
I think that is very different than an app with good keyboard shortcuts btw which is why, for example, despite many editors having great keyboard shortcuts I keep going back to vim. So I’m Making basic apps that are intended to be used entirely with a keyboard and just happen to support mouse input too.
I realize this doesn’t work well for everything but my todo app and my note taking app should work great at least.
Earlier quoted context omitted.
> What about things like manipulating files and running programs? Aren't they the things people do with computers? I'm confused. Manipulating files and running programs is a given, isn't it? You mean ls/cp/mv/rm-style? And running programs is... type in the name of the program (if in $PATH) or its path (if not) and press enter. Why would anyone bother blogging about that?
It depends on what people use the GUI for. It's not inconceivable that people start up gvim to make a new file (instead of cat > file) or use some bulk-renaming tool instead of learning about shell expansions. "Awful" was a mean description of this article. I'll fix it (edit: comment, not fix).
touch file
You can quickly invert this to read as: GUI configurations to break your dependence on the command line.
In moment's thought, it becomes very obvious that a GUI can readily conceal complexity and require earned skill in the same way any text mode interface might. Text command skills also evaporate just as quickly when you realize you were just locked into preferences specific to the system they bind to.
The command line is not better than other ways of completing tasks. When Linux (and each and every last variant) dies (however long that may take), it will become all too obvious that the essential commands people memorized were only useful within the scope of that particular operating system
This article is awful. You're not going to "break your dependence on the GUI" by replacing 5 things you do a few times a day with obscure, less good CLI alternatives. What about things like manipulating files and running programs? Aren't they the things people do with computers? Also, bc is especially terrible. Nobody who is already "dependent on the GUI" is going to want to know about scale= and all that. Better to…
> What about things like manipulating files and running programs? Aren't they the things people do with computers? I'm confused. Manipulating files and running programs is a given, isn't it? You mean ls/cp/mv/rm-style? And running programs is... type in the name of the program (if in $PATH) or its path (if not) and press enter. Why would anyone bother blogging about that?
(Ok, it’s a bit cheating, sort of text/GUI, but makes file manipulation so easy on console)
This article is awful. You're not going to "break your dependence on the GUI" by replacing 5 things you do a few times a day with obscure, less good CLI alternatives. What about things like manipulating files and running programs? Aren't they the things people do with computers? Also, bc is especially terrible. Nobody who is already "dependent on the GUI" is going to want to know about scale= and all that. Better to…
> What about things like manipulating files and running programs? Aren't they the things people do with computers? I'm confused. Manipulating files and running programs is a given, isn't it? You mean ls/cp/mv/rm-style? And running programs is... type in the name of the program (if in $PATH) or its path (if not) and press enter. Why would anyone bother blogging about that?
In other words, things a typical GUI file manager can do easily.
I'd like to note that no manual at all is needed to understand a basic menu structure or a GUI system with consistently used widgets.
Earlier quoted context omitted.
> What about things like manipulating files and running programs? Aren't they the things people do with computers? I'm confused. Manipulating files and running programs is a given, isn't it? You mean ls/cp/mv/rm-style? And running programs is... type in the name of the program (if in $PATH) or its path (if not) and press enter. Why would anyone bother blogging about that?
How about finding out what files are there in the first place, what data the files represent and which programs would be useful to operate on the files? In other words, things a typical GUI file manager can do easily.
ls?
> what data the files represent
ls, file
> which programs would be useful to operate on the files?
I guess I assume that people know this kind of thing, but xdg-open is fine.
Earlier quoted context omitted.
> What about things like manipulating files and running programs? Aren't they the things people do with computers? I'm confused. Manipulating files and running programs is a given, isn't it? You mean ls/cp/mv/rm-style? And running programs is... type in the name of the program (if in $PATH) or its path (if not) and press enter. Why would anyone bother blogging about that?
It depends on what people use the GUI for. It's not inconceivable that people start up gvim to make a new file (instead of cat > file) or use some bulk-renaming tool instead of learning about shell expansions. "Awful" was a mean description of this article. I'll fix it (edit: comment, not fix).