XP is just a number | |
PerlMonks |
comment on |
( [id://3333]=superdoc: print w/replies, xml ) | Need Help?? |
Thank you, everyone, for your comments, suggestions, and/or support.
I've been mulling this over for quite some time; this isn't the first time that I've gotten some flak for using or wanting to use a "scripting" language in an enterprise application. I suppose that my problem really consists of two things:
What I'm actually fighting is a mindset. It's not that they don't know how or can't learn to code in Perl; they're just the kind of people who'll buy the first thing the vendor drops on the table and insist we use it, for better or worse. I've decided to press the issue further, perhaps using subversion ("Oh, uh, I've already written a prototype in Perl... is that OK?"), or perhaps going the business route and making a dollars & cents case, or maybe both. It matters to me on a somewhat personal level, not because I'm a proud Perl zealot or Java basher, but because I've recently agreed to move for the company and I've signed a contract obligating me for the next year. I personally don't want to live with and maintain crappy, troublesome software, de facto, for the next year. Is this pursuit dangerous? Maybe. Is it worth it? Maybe. Only those who will risk going too far can possibly find out how far one can go. -- T.S. Elliot higle Can I crash at your place if this backfires? -- Higle In reply to Re: Perl vs Java in Heavyweight Filesystem Processing
by higle
|
|