For me, the strength of Perl 5 in 2018 is that the code I am writing today looks quite different from the Perl 5 code I've written a decade ago, but the code I've written back then still works. The language evolves, and I can follow - in my own time. I don't have to convert my old classes to Moose but I can, and quite often I do because the code is so much more readable. I don't have to convert CGI programs to PSGI or to one of the web frameworks, but I can, and occasionally I do. And so on - other monks have provided plenty examples of modern Perl 5.
With Perl 6, we have Inline::Perl5, and maybe soon-ish a Perl 6-aware IDE, so I can use all my old stuff in new programs where I exploit those Perl 6 features which are somewhat cumbersome in Perl 5 (notably grammars and concurrency). So the journey just goes on. Modern Perl 5 has been heavily influenced by Perl 6, so the chasm that existed between the two languages ten years ago is now a gap that can be jumped over. And again, I can jump if I want, I don't have to. This makes me absolutely relaxed with regard to selecting a programming language, and I like that.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|