Warning

 

Close
Confirm Action

Are you sure you wish to do this?

Cancel Confirm
AR15.COM
5/22/2013 12:03:22 AM EDT
In about a week or two, we retire our mainframe, a command driven system. Tonight, I asked a junior worker if he had ever seen a command driven system, if he wanted to see one, but he assured me that he had.

True, there are still such systems out there such as if one is loading up operating systems to servers (what's suppose to be one of my next jobs).

But for most the world, it's menu driven. One clicks on a tab and if there are more options, a list drops down to tell you what can be done.

As a computer user, I prefer command driven systems. I don't want the computer to tell me what it can do, I want to tell the computer what it will do.

But........as a programmer, I prefer menu driven systems................so the user can't mess up my work!

What about you?
______________________________________________________________________________________________________
("Type this! Direct to CPU   Cancel!"--Dr. Carol Hanson trying to stop Moffet's virus program, (w,stte), Airwolf, "Moffet's Ghost")
5/22/2013 12:06:52 AM EDT
[#1]
Command line all the way. Building a GUI is a huge annoyance to me.


5/22/2013 12:07:30 AM EDT
[#2]
The option of both.
5/22/2013 12:12:28 AM EDT
[#3]
For work and light hearted fun I prefer menus. Give me purdy colors and a slick GUI, and I'm good to go. I'm still quite capable with DOS and other command line things though, and I play DOS games regularly through DOSbox, which is nerdier than the majority of the "gaming" population.
5/22/2013 12:15:48 AM EDT
[#4]
I COMMAND, IT EXECUTES!
5/22/2013 12:21:40 AM EDT
[#5]
The user will always fuck you up.



Command based or GUI, the outcome is only as good as the programming.



You said the mainframe is going away - is it AS400?
5/22/2013 12:39:27 AM EDT
[#6]
CLI for configuring. GUI for monitoring/analysis.
5/22/2013 12:59:53 AM EDT
[#7]
I'm a UNIX admin.  For admins, menus are fine for convenience, as long as you understand what they are doing under the covers. For the typical user, CLI's are pretty much a thing of the past.

Command line stuff was greatly complicated when some idiot had the bright idea to make a space a valid character in a file/path name.  


But then, I guess I'm a dinosaur. I still use 8.3 filenames.  
5/22/2013 2:02:30 AM EDT
[#8]
Both !
For configuring critical things - CLI,for daily basis-GUI .
5/22/2013 2:14:40 AM EDT
[#9]
TRSDOS for the win!!!!!!!!!!!!!!!  I never should have sold my TRS-80 Model 4.

5/22/2013 2:20:14 AM EDT
[#10]
Quoted:

Command line stuff was greatly complicated when some idiot had the bright idea to make a space a valid character in a file/path name.  




That god damn space in command line    You had me LOL in my office thinking of all the times it was a f'in space in the line..........

But in reality I like option of having both, we just recently brought are old ALPHA down and I dont miss it one bit.

5/22/2013 2:47:59 AM EDT
[#11]
Quoted:
I'm a UNIX admin.  For admins, menus are fine for convenience, as long as you understand what they are doing under the covers. For the typical user, CLI's are pretty much a thing of the past.

Command line stuff was greatly complicated when some idiot had the bright idea to make a space a valid character in a file/path name.  


But then, I guess I'm a dinosaur. I still use 8.3 filenames.  


bash-3.2$ touch " -rf ."

*tells local idiot admin to go and delete that*

*whistles innocently and awaits the carnage"
5/22/2013 3:29:39 AM EDT
[#12]
In my previuos life:   On my iSeries, AS400, Users DON'T get Command Lines!!!!
5/22/2013 3:40:44 AM EDT
[#13]
As long as said menus are running on a command line system, I'm good to go w/ menus.  I spent my early adolescent years wearing out the man command in various Linux distros.

5/22/2013 7:43:14 AM EDT
[#14]
Girls Use It

j/k