Here is my take on the languagues:
Perl - Basic on steriods, instant gratification and debugging
- Got a bad wrap in CGI circles because it was so easy to
- do CGI stuff that lots of people did - BADLY
C - THE language that made programming what it is today
- All the power of assembler in a (slightly) more user friendly package
ASM - Everything ends up here. To code C you need to have
- a handle on the guts of the system anyway
C++ - C extended to do OO better. Unnecessary for single programmer
- as you can do it in C in half the code (procedural)
- Forces you to be OO which is not needed for short stuff
- It is way easier to do multi-programmer stuff OO with solid APIs
- Yeah, yeah what starts little often suffers featuritis
Java - C++ with all the power toys taken away. Comiles to bytecode not ASM
- Supposed to be portable but MS got involved ;-)
- speed not that great due to partial compilation
- TRENDY in management circles.
Here is a nice one liner for you:
perl -pi.bak -e 's/something/otherthing/g' <FILE LIST>
That particular snippet does a search and replace on a list of files writing a backup to filename.bak in the process. Handy and 100s of times faster than doing the same in a Windows based editor.
cheers
tachyon
s&&rsenoyhcatreve&&&s&n.+t&"$'$`$\"$\&"&ee&&y&srve&&d&&print
In reply to Re: Re: Re: Should I learn Perl?
by tachyon
in thread Should I learn Perl?
by Anonymous Monk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |