My point wasn't that perl6 can't be learned, just the opposite, that
it must be *learned*. And that knowing perl5 won't be much
of a help. To put it another way: Once my shop switches to
perl6, a new hire that only knows perl5 has no real advantage
over a new hire that only knows python. Both will have to *learn*
perl6.
People who keep arguing about how trivial it will be to convert
perl5 code into working perl6 code belittle the fact that perl6
will be a new language and that switching to perl6 will involve
a lot more than just writing perl5 in perl6. A perl5 programmer
moving to a perl6 shop probably has as much of a learning curve
ahead of them as a perl5 programmer moving to a python shop (or
a python programmer moving to a perl6 shop for that matter).
I don't have a problem learning perl6, and I've kept up with
perl6 development as best as I can. I have a problem with
people who trivialize what the cost of switching to perl6
will entail.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.