|Perl: the Markov chain saw|
Re: Perl 5 Optimizing Compilerby flexvault (Monsignor)
|on Aug 13, 2012 at 13:36 UTC||Need Help??|
From my observations, Perl gets better with each new version, and if you use Perl's strengths, you can leave many 'off-the-shelf' 'C' programs in the dust.
But, I would love to see a Perl compiler, but not for speed or concealing the code from hackers, but for code security, revision control and simplicity of deployment. ( and probably a few more. )
Before Perl, I used 'C' and 'uxbasic', a 'compiler' that mimicked the Z80 based 'oasis/theos' basic from the '80s but could run on most AIX/Unix systems. It could be run from source (BASIC), from an interpreter compiled code (BASICOBJ), and from pseudo compiled code (BASICCOM). As a developer you tested with the first 2 modes and then shipped the final version as the pseudo compiled code (think bytecode). And guess what, if the run time version of 'uxbasic' was installed, the code you shipped worked.
Now I'm not comparing this '80s code to Perl, but that concept of distributing code would improve the user experience with Perl. Why?
Since the '80s, I have sold and supported software for companies, the majority of which have 10 to 100 employees. They also have 1 or more people who have used Perl to print "Hello World". Since I started shipping Perl modules, I've had some of the funniest (maybe tragic) updates to my software. For example:
"Well done is better than well said." - Benjamin Franklin