in reply to Space taken by a coderef

I am interested to know why you are concerned about this? Memory is cheap and plentiful. Perl hogs memory anyway, so worrying about the small stuff usually isn't important imho. I like chicken.

Replies are listed 'Best First'.
Re: Re: Space taken by a coderef
by tradez (Pilgrim) on Jan 18, 2002 at 23:29 UTC
    Thoughts like this are what is going to keep perl from going into a production respected language. We at my company have recently had to completely recode our entire backend because the coding was done so loosely, that when put into production with actual customers, we were eating up gigabytes of ram with all the forking and bg processes that were taking place. RAM is not THAT cheap when you start having to purchase terrabytes of it just to work around sloppy code.
Re: Re: Space taken by a coderef
by elwarren (Priest) on Jan 18, 2002 at 21:59 UTC
    Cheap memory is no excuse for sloppy code. Nuf said.
      I really don't think that is 'nuff said. In fact I said quite a bit more about the topic at Re (tilly) 1: What does "efficient" mean?!?, as well as in other nodes.

      As obvious as it may be to you that you should never be knowingly inefficient, optimizing for the wrong problem is a waste of overall resources.

      If you disagree, then I invite you to look at the memory use of Perl and decide to work in C and assembler until you see the light.

        Well at least you have a more mature response than others. This is off topic from the orig thread, but...

        Tradez makes my same point a post or two below mine.

        My issue is that in my job I see applications developed that require multiple servers with gigabytes of ram to run when they could run off of one server. The only reason this happens is because the application developers were sloppy. The "Ram is cheap and it's not my dime anyway!" attitude caused this. We brought in another group to do code review, optimized their code, and now the same app runs even faster on a single machine. The other two machines have been allocated for growth as opposed to a requirement to run.

        There's something to be said about taking pride in your work. The "ram is cheap" attitude seems to me to go against the general attitude of the Perl monks, "how can I do this, or how can I do it better?"

        While this coderef question may not be a good example, it should still not be easily dismissed without a real answer in a place where questions are welcomed.