<div>That's a good point.</div>
<div> </div>
<div>It would be near impossible to sell a Perl solution where I work, but when we're in a crunch and it saves the day, no one seems to mind.<br><br> </div>
<div><span class="gmail_quote">On 7/19/07, <b class="gmail_sendername">Chuck Day</b> <<a href="mailto:Chuck.Day@s1te.com">Chuck.Day@s1te.com</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">I've been one of perl guys that are forced to use other crappy tools and languages.<br>However when something needs "done" I can always knock it out in perl before they
<br>can have a meeting about what high priced tool to use. Forget about how much time<br>and money we're wasting talking about it. I've even stuped to using a .asp<br>extension for a couple perl apps. Just added this to apache:
<br><br>AddHandler cgi-script .cgi .asp<br><br>I have absolutely no objection to jobs being posted here.<br><br>Charles<br><br><br>><br>> On Jul 18, 2007, at 5:10 PM, Jonathan Hogue wrote:<br>><br>>> good discussion. I was having this same conversationon the side.
<br>>><br>>> To me, there's two points. perl's bit of a dieing language. ie,<br>>> most new projects are in Java, .net or maybe Ruby. Most companies<br>>> that do perl are in a containment mode or are in the process of
<br>>> converting to some other technology. And a lot of the talent that<br>>> used to do Perl are now doing other things (java, .net, Ruby or<br>>> something completely different).<br>><br>> Sometimes I ponder on that "dieing" thing. One doesn't see too many
<br>> perl articles on dzone, digg, etc. But is that because the other<br>> languages don't have things like local perl monger's groups (I know<br>> CMH has a Ruby group now), perl Monks, use.perl and the best tool of
<br>> all cpan? How many of those other languages that are always being<br>> blogged about have the vast resources that cpan gives perl, available<br>> to them - now?? Or is it because instead of blogging about 10
<br>> different variations of the same simple sets of ruby/php code, people<br>> are actually just coding away in Perl instead of blogging about it?<br>><br>> I guess it all depends on where you work. Some places are Perl shops.
<br>> Some vb, .net, rails, java, c, whatever. Each has many frameworks,<br>> that different shops choose (or not) to use.<br>><br>>> I haven't worked in Perl in over 2 years. My experience is out<br>>> dated. So most perl interviews are a waste of time because they end
<br>>> up being dead ends.<br>><br>> But how many years did you spend coding in it? How fast, if you<br>> wanted to, do you think you could "pick it up again"?<br>><br>>> Also, because Perl is being used less and less in application
<br>>> development projects, and by doing Perl development I'm missing<br>>> opportunities to learn more marketable technologies, it's a bit of<br>>> a dead end career move to.<br>><br>> I think it depends on where you work. But most places I've worked -
<br>> learn something new? 'Do it on your own time.' Then they don't<br>> understand why you get hired away at a larger salary because you know<br>> more and you're more valuable. Hmmm. Seems like a pattern to me, but
<br>> what do I know? ;) (as I pickup another programming book)<br>><br>>> That doesn't mean that I won't take Perl positions, but I look to<br>>> be paid a premium ($150-300 an hour) to even consider going through
<br>>> the interview process and jumping into a position whose main<br>>> benefit is the pay.<br>><br>> Heh, I've never been paid to consider/go through an interview<br>> process. My hats off to ya :)
<br>><br>> Shane<br>><br>><br>><br>>><br><br><br><br>_______________________________________________<br>Columbus-pm mailing list<br><a href="http://columbus.pm.org/">http://columbus.pm.org/</a><br><a href="mailto:Columbus-pm@pm.org">
Columbus-pm@pm.org</a><br><a href="http://mail.pm.org/mailman/listinfo/columbus-pm">http://mail.pm.org/mailman/listinfo/columbus-pm</a><br></blockquote></div><br><br clear="all"><br>-- <br>Jonathan Hogue<br><a href="mailto:jon@hogue.org">
jon@hogue.org</a><br>740-474-9170