My first long-term job was Unix programming (in despite of fact that first money for code I got for Z-80 chip programming (some little hack of Z80 in beginning of 90'th )).
Thats way I prefer the command line tools.
I think GUI does not have real performance in tasks of programmer, also GUI skills can not be reused when you need automate your task you done before by clicking.
If you typed instead, you can put your typing in the script and make the script working for any count of times.
However I found in my practice some cases when GUI was better than command line for development.
1) Development of GUI
I have experience of the development of tools for the internet trading, that were mouse based and highly interactive. And visual tools for visual development were really much progress in comparison to writing code for forms definition. In such RAD tools for the GUI, GUI interface and the visual development environment is the must.
However, I know that for experienced traders command line tools were much more comfortable.
They used command line tools for trading instead of GUI, if they had the choice.
2) GUI for understanding new tool.
Visual GUI wrapper around CLI can be helpful when you are learning new tool.
Of cause output/actions log window in the CLI form is the must, to be able than do the actions from the command line.
3) GUI as wrapper around family of CLI tools, that are based on some concept, however using different syntax. For example, uniform interface around sccs/rcs/cvs/svn/git/ and so on,
helps you to avoid switching contest errors, when you have to maintain systems, based on different version control tools.
However, CLI wrapper would be even more helpful :)
Monday, May 19, 2008
GUI vs. Command Line, similiarity in tools
Posted by Roman G. at 8:41 AM
Labels: concepts, GNU/Linux, Language comparison, usability
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment