|Problems? Is your data what you think it is?|
Perl 5 Compiler, Again!by flexvault (Monsignor)
|on Aug 13, 2012 at 17:39 UTC||Need Help??|
flexvault has asked for the
wisdom of the Perl Monks concerning the following question:
I started the day thinking of other things, and the first thing I read was Perl 5 Optimizing Compiler by Will_the_Chill and I stated my opinion. So instead of doing real work, I thought about this question/problem about a compiler for Perl.
But instead of going after the obfuscation angle, I'd like to ask the Monks that understand the internals of Perl, why this is so elusive. Just to be sure, I did read the references in the discussion, but I still have some fundamental questions:
The computers today are very fast, and I expect will continue to get faster, so converting Perl to C may or may not be needed (Others can decide/argue that point). I work on many computers today, that whether I execute a 'C' program or a Perl script, I get an immediate prompt, so do we care whether it took 200ms or 300ms.
Whether 'Big Data' needs a Perl to C compiler I don't know, and I think Perl is the best computer language I've found, but I also think that a built-in bytecode 'compiler' would enhance Perl greatly, but I also realize that there may be many valid technical reasons why it can't be.
"Well done is better than well said." - Benjamin Franklin