I think you hit a good example of when perl outpaces bash. If you are writing applications with options, bash is much harder and a lot less clean than GetOpt in perl.
But I still think it's worth it to learn bash. Or more specifically, 'ksh'. The differences between bash and ksh are small, so think of ksh as the subset. (Off the top of my head, the main difference is forking a process during a while read.) At any rate, the reason shell programming is worth learning is because learning shell means learning unix commands. I'm astounded by the number of perl people that can navigate File:: cpan modules but can't write a decent find on the command line.
Also, when you learn both, you get the best of both worlds. Your shell applications can call perl and vice versa. Mix and match as needed.
--
I used to drive a Heisenbergmobile, but every time I looked at the speedometer, I got lost.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.