Re: Perl Network Programming: A Dying Craft?by crazyinsomniac (Prior)
|on Jul 01, 2001 at 05:17 UTC||Need Help??|
Depends on who you're talking to.
Now don't get me wrong, learning true socket is something every programmer should do, and perl is a good language to learn it in, but as for marketability in the business world, seems kinda insignificant (at least for the majority of the busines market).
Why, because one of the reasons Java was made was for real-business type network applications, and perl simply wasn't.
I'm talking about enterprise-wide network application, Remote Method Invocation and stuff like that.
While I am talking out my a$% most of the time, in general, Java applications are easier to maintain, develop, and debug, particularly because of the 'abstraction' Jeffa mentiones, which while not being particularly exciting, and limiting, provides a sense of safety from real bugs.
Java also makes scalability, granularity, and distribution easier.
A lot of programmers like to get away from the dirty details, and business people like their programmers to concentrate on the important details, like adding numbers, and not reimplementing already stable components.
One of the reasons people are moving away from perl for quicky network applications is because they don't want them to be just quicky applications, and java makes making that distinction easy.
>Will it significantly enhance one's marketability to know it?
But some kind of manager, business non-programmer person type, will once again go for the buzz words, and he won't be particularly interested that you know some arcane technical details.
So, in conclusion, learning Perl Network Programming is a dying 'craft', but one which will get you respect from real programmers, and a few laughs from the business ones.
However, while it may seem a dying craft, people still program in COBOL, but them jobs are few and far between (not true for perl quite yet, but the tide is turning).
It can't really hurt to know important details, even if it might appear that way.
And don't forget, some c/c++ programmer had to write Java, and the many Java Native Interface extensions, as Java can't handle everything (whereas perl pretty much can, network programming wise at least, and easier than c/c++).
I would like to remind you of my little disclaimer, so do take some of this with a grain of salt, as it is an extremist view coming from an extreme (and biased) programmer with limited experience (after all, aren't all/most human beings such creatures?-).