(Untitled)

[turboslut]

On a random stop at Barnes and Noble on Sunday, I picked up this book - Windows Command-line Administrator's Pocket Consultant.

The clerk who rang it up for me took one look at it, laughed in my face - literally - and said "Windows command line? Who still does that?"

I need a job working on Unix machines so very, very badly.

Comments

[unsi_sempai]

You should have said, "Which one of us is working in the industry, asshole?"

[unsi_sempai]

I'm sorry, it should be "Who here works in the computer industry." That's way funnier.

[decklin]

I think I'd rather work in a bookstore than not on unix, personally.

[turboslut]

It's not that bad. I miss doing things quickly via text, but waiting for bloated Windows GUIs to load gives me plenty of time to do things, like read webcomics and contemplate why I still bother with this job.

[deadend56]

I feel your pain, I have to use the windows command line all the time (stupid 80 character line limit). I found a good trick to get around *some annoyances is to install cygwin, and ssh into the windows machine from an x server enabled machine. That makes life at least somewhat tolerable.

Command Shell

[vhalros]

They are finally revamping it in Vista. I'm not sure why it took them 10 years to figure out that GUI's are retarded for batch jobs. It actually sounds sorta (in theory, any way) cool. The commands are supposed to provide some API or another, so you can actually except some sorta consistency out of them, and pipes between commands actually get .Net objects sent over them (isntead of unstructured bytes). THere is an overview of it here: http://arstechnica.com/guides/other/msh.ars .

[rashind]

Silly boy, Windows doesn't even have command lines.

/Win95 commercial

[greypaw]

LOL!