"Examples?'"mkdir -p directory/{1,2,media/{tv,movies,pictures}} ; mv ./*.mov ~/directory/media/moviesThat took me all of 20 seconds to write when it would of took me at least a couple of minutes in the GUI
Excellent example to illustrate the fundamental philosophical differences between *nix and WIndows. Obviously, Windows is more focused on ease of use, *nix is more focused on efficiency. Both have their place. It all comes down to what people expect from computers and technology. Should users accomodate the computer or should the computer accomodate users? Which is more important, user efficiency or computer efficiency? Which is more valuable, computer skills or problem solving skills? Which philosophy will most people embrace? Which will form the basis for computing in the future? The answer is particularly significant for anyone who plans to earn a living from computer technology.
Nice to have a list to go by, figuring I have not runLinux for a little over a decade, now am usingUbuntu.I remember when Linux was mainly text based distros.
"I think you can get the best of both with the standard Linux method of making a powerful and versatile CLI program to do all the real work, and a separate graphical interface that uses the CLI program."I haven't bothered to study the low level implementation details of Linux GUIs but I can't imagine that they actually rely on the CLI tools very much at all. My guess is that for the most part, they provide their own separate, alternative implementations.For example, to obtain a list of files, does KDE launch and interface with the CLI "ls" app? Seems to me like this would be horribly inefficient. Instead, I suspect that KDE builds it's own interface with the file system driver through the kernel.
redhatcatAug 27, 2006
'"but there are a lot of more advanced things that simply cannot be done in a point and click interface." Examples?'Scripting.
Closed AccountAug 28, 2006
"Examples?'"mkdir -p directory/{1,2,media/{tv,movies,pictures}} ; mv ./*.mov ~/directory/media/moviesThat took me all of 20 seconds to write when it would of took me at least a couple of minutes in the GUI
jqp123Aug 28, 2006
Excellent example to illustrate the fundamental philosophical differences between *nix and WIndows. Obviously, Windows is more focused on ease of use, *nix is more focused on efficiency. Both have their place. It all comes down to what people expect from computers and technology. Should users accomodate the computer or should the computer accomodate users? Which is more important, user efficiency or computer efficiency? Which is more valuable, computer skills or problem solving skills? Which philosophy will most people embrace? Which will form the basis for computing in the future? The answer is particularly significant for anyone who plans to earn a living from computer technology.
jogeekAug 28, 2006
how many times are we going to post this site on Digg?<a class="user" href="http://digg.com/tech_news/The_COMPLETE_command_line_list_for_Linux,_Windows,_Oracle,_and_MacOS">http://digg.com/tech_news/The_COMPLETE_command_line_list_for_Linux,_Windows,_Oracle,_and_MacOS</a>pretty sure I've seen it before this post too.
nkassiAug 28, 2006
Also, "FULL" command list. Bulls**t. The universe of Linux command is much bigger. "Common" comand list" would be more apropriate.
innovafandgAug 28, 2006
Nice to have a list to go by, figuring I have not runLinux for a little over a decade, now am usingUbuntu.I remember when Linux was mainly text based distros.
agretAug 29, 2006
@asdf25 it is the FULL list after all, the digg story isn't called "Linux Commands - A short list" like it should be....
jqp123Aug 29, 2006
"I think you can get the best of both with the standard Linux method of making a powerful and versatile CLI program to do all the real work, and a separate graphical interface that uses the CLI program."I haven't bothered to study the low level implementation details of Linux GUIs but I can't imagine that they actually rely on the CLI tools very much at all. My guess is that for the most part, they provide their own separate, alternative implementations.For example, to obtain a list of files, does KDE launch and interface with the CLI "ls" app? Seems to me like this would be horribly inefficient. Instead, I suspect that KDE builds it's own interface with the file system driver through the kernel.
treeheadSep 5, 2006
This is not a full list. Not even close. No digg.