|
in reply to Re^3: Should I come back to Perl?
in thread Should I come back to Perl?
\o,
well, Node.js ... I never liked server-side JavaScript. The thing that annoys me most with Python (any version) are the missing brackets. :-)
I do like Perl 5, always have, probably always will. I've just been out of the game for quite a while now. While the languae itself doesn't seem to have evolved much (although I still need to dig through the recent feature additions), Perl6 was not a subject when I last left Perl.
So, basically, Perl6 is "Perl 5+ in a VM"? (VMs are awful IMO.)
Regards and all that,
jkl
|
Re^5: Should I come back to Perl?
by Laurent_R (Canon) on Sep 11, 2015 at 17:09 UTC
|
So, basically, Perl6 is "Perl 5+ in a VM"?
No, really not. Perl 6 is really a different language, with a clear parenthood with Perl 5, but yet a different language, more expressive, more modern, with many new features, including a full-fledge object system, grammars, lazy lists and arrays, features from functional programming languages, etc. I think the comparison with C vs C++ made by another monk is quite illustrative of the difference between the languages.
Although I am very interested with Perl 6 and am trying to contribute to the Perl 6 community, I haven't coded anything really serious (i.e. production code) in Perl 6. For example, I'm not using Perl 6 for my job, whereas I am using Perl 5 almost everyday (and most of my days) at my job. I certainly don't see Perl 5 to vanish away in any foreseeable future.
As for the VM, this is not really the essence of Perl 6, it is just the current implementation that is using a VM. A future implementation might be entirely different.
| [reply] |
|
|
| [reply] |
|
|
I guess this comparison with Pascal and Ada is indeed more accurate (although comparing Perl 5 with Pascal seems a bit awkward to me). But I only said that the comparison with C and C++ was "illustrative", meaning simply that it conveys the general idea that the P5 and P6 languages are different, although obviously sharing a lot of ideas, having a somewhat similar syntax (at least superficially) and belonging to the same family.
| [reply] |
Re^5: Should I come back to Perl?
by Your Mother (Archbishop) on Sep 11, 2015 at 16:53 UTC
|
Perl6 has the potential to be amazing and could include cross-compilation and such. It's not baked yet. Pretend it doesn't exist. Serverside JS is a bigger threat to Perl than Perl6, Python, and Ruby combined; it's the only full-stack high-level language and its tools are constantly improving.
Perl5 has had various speed and minor feature enhancements in 10 years but the ecosphere/CPAN (especially web stuff) has changed dramatically in the last 10 years.
| [reply] |
|
|
| [reply] |
|
|
Short version: there was no Moose, no Moo, Catalyst was still new and relatively unknown, no PSGI, no Dancer, DBIx::Class was just forking from Class::DBI, no Mojolicious, the template space was completely stalled, the file handling space was old school File::Find, tools like Proc::Daemon were fairly sucky and unlikely to work on your platform (it’s an *excellent* tool today), CGI.pm had been the defacto standard for 15 years (counting cgi-lib). Circa that time, the core Perl team was in disarray and regular releases were a fantasy. Best practices was a fairly foreign cultural concept still—it’s often in stark contrast to TIMTOWTDI—and just gaining traction. There is hardly any generic code from 2005—not talking custom algorithms, one-offs, etc—that couldn’t be better written with the CPAN and generally accepted practices of today. Perl had one foot solidly in the grave around 2003. Soon thereafter it started to experience a renaissance that is still in progress.
| [reply] |
|
|
|
|
|
|
