Re^3: Advice of picking the language for my job, please

Like I said before, we have tried this before and Perl has some serious efficiency issues with respect to PostGres. When you start getting large data sets back it will simply crash. Also since we noticed that the current PostGres CPAN modules were buggy we decided that instead of re-writing them in PERL we would just go ahead and do it in C. Of course it all boils down to design preferences and what the Developers are comfortable with.

Comment on Re^3: Advice of picking the language for my job, please

Replies are listed 'Best First'.
Re^4: Advice of picking the language for my job, please by Ardemus (Beadle) on Feb 04, 2005 at 18:50 UTC
I'm sorry that you've been downvoted for your comments. Another poster has reported similar experiences with perl/PostGres and no-one has posted about their first hand success with the combination. I appreciate your impartial comments, and I'm a little ashamed that our order disaproves. Ardemus - "This, right now, is our lives."	[reply]
Re^5: Advice of picking the language for my job, please by BUU (Prior) on Feb 04, 2005 at 19:35 UTC
I appreciate your impartial comments, and I'm a little ashamed that our order disaproves. If I may take a guess at speaking for the rest of the monastery, people don't disaprove of "impartial comments", people disaprove of comments that seem to attack Perl with out providing any evidence what so ever. No evidence to exactly what he was doing, or how he was doing it or what actually happened, merely "large datasets seemed to crash". Just for example, sucking 10gigs of results in to ram would probably crash most computers, regardless of the language. If he had provided clear, specific examples as to what he did, what happened and why he thought it was wrong, people wouldn't downvote him, and it might even get fixed!	[reply]