Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

jmcnamara (659)

jmcnamara
  (email not shown publicly)
http://search.cpan.org/author/jmcnamara/

'ere I am, J.M.! The ghost in the machine:

perl -MCPAN -e 'install jmcnamara & _ x ord $ ;' | tail -1

Journal of jmcnamara (659)

Thursday June 17, 2004
06:04 PM

Thanks for all the (managed) memories.

[ #19333 ]
In the middle of a "Joel on Software" article about How Microsoft Lost the API War is an interesting assertion:

Whenever you hear someone bragging about how productive their language is, they're probably getting most of that productivity from the automated memory management, even if they misattribute it.

I think that this applies very much to Perl. The productivity not the bragging.


List all Journal entries
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Thanks for all the (managed) memories. 2 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.

  • That implies that all languages with automatic memory management are equal. And if you program in more than one, you would still have an opinion on how much more productive you are in one or the other.. take Perl and Python, for instance. Or even Java.

    I think that is too simplistic a view, possibly. Automated memory management is one of a (mid sized) laundry list of features that one should (or could) use to decide on suitability and productivity. You get minus points for some classes of tasks (managing me

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.