I reckon that using command line tools properly is one of the signs of a good programmer. Even though I know this I have never really put concerted effort into learning about them.
I have always worked on windows as my primary dev platform - maybe that's why. Windows command line support is crap. The same old cmd.exe that has been there for years. Difficulties scrolling, adjusting the amount of detail you see etc. It is as if the people at Microsoft never thought that an expert is going to use our software. Someone who is not afraid of sharp edges and speed.
Powershell came along then. Seemed like a big improvement, but after my initial excitement it turned out to be squarely pointed at sysadmins of which I am not one.
I heard about cygwin years ago and have used it a little, but not to the extent that I get to on the current job. It's not as good as working in a proper unix shell (I use Ubuntu at home, so know what the good stuff feels like) but it is a huge leap from the muck that comes with windows out of the box. What's really disappointing about windows command line support is that they have been touting various resource kits for years. They seem to consist largely of the command line tools that their platform lacks. Would it have been a huge step down to just include these tools in the default distro and concentrate on the flashing lights?
Anyway via cygwin I am getting to use sed for my work. This is a pleasure. Not an easy one, but worthwhile all the same. I used it in anger - well productivity as it happens - just today. I need to keep piling on the command line experience and knowledge. That's the way to be a satisfied nerd.
No comments:
Post a Comment