in reply to [Quote] When should I use Perl?
And once you have your "First System" up and running, then is the time to decide whether or not it's worth while to re-write something works and something that people are familiar with in C/C++/Java.
I am very fond of building mock-ups of The System in Perl so the various parties can all get their hands on something early on in the design process. Changes are much easier in scripting languages. I can give Them almost instantaneous feed-back ("Here it is in magenta; (click-click) now here is puce"). And if my "mock-up" is good enough, I get my System designed and out the door that much faster.
Yes, it's not as "fast" or as "sexy" as it might be if it were written in C/C++; but it's here, right now, in your hands; not sixteen months (if we are very lucky) away. Yes, The System is written in Perl (or Python or Visual Basic or REXX) -- so? It serves our needs now while the new super-whiz-bang is being developed by the Crack Infrastructure Development Team. Think of it as a bridge between today and the day that the Crack Team finishes....
I have had a lot of experience in bridge-building. And I build them as if I will be using them still in five years time. I may over-engineer my bridge a bit, but I get to sleep better at night because of it.
----
I Go Back to Sleep, Now.
OGB
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^2: [Quote] When should I use Perl?
by blazar (Canon) on Dec 27, 2006 at 13:09 UTC | |
|
Re^2: [Quote] When should I use Perl?
by bibliophile (Prior) on Dec 27, 2006 at 14:46 UTC |