Ready to be published? LXer is read by around 350,000 individuals each month, and is an excellent place for you to publish your ideas, thoughts, reviews, complaints, etc. Do you have something to say to the Linux community?
This is the first in a series about using the "command line" in Linux. It is also about knowing when to use a gui instead. But before going into any of that we need to understand what is meant by a "command line" application. You'll find that as we explore that idea, a lot of things that are not really true 'cli' (command line interface) apps arguably count as cli, including menu driven console based apps and even gui apps. This will be controversial. Let's start with some basic definitions. If anyone has any problems with any of the following just let me know. Consider this a first draft subject to revision!
Very nice, he defines terminology and even has a bit of funny, "Tom Clancy Popout".
My job is getting ever-more vexing because they use a lot of Web apps, ghastly slow Web apps that live on slow servers and only let you do one thing at a time, and are moving everything to some kind of horrid Web interface. And this is the Bright Happy Future so many pundits are predicting. Ain't nuthin happy about it, it's like going from power tools to dull spoons.
kind of looking forward to the next installment(s)
Post a comment
A free account is needed to post. Write your comment here first: your text is kept in this browser while you sign up or log in, and is waiting for you when you come back.
Your message:
|||||
10
Markdown: **bold**, *italic*, [text](https://link), - lists, > quotes, $x^2$ for math. Formatting help
My job is getting ever-more vexing because they use a lot of Web apps, ghastly slow Web apps that live on slow servers and only let you do one thing at a time, and are moving everything to some kind of horrid Web interface. And this is the Bright Happy Future so many pundits are predicting. Ain't nuthin happy about it, it's like going from power tools to dull spoons.