Come for the quick hacks, stay for the epiphanies. | |
PerlMonks |
Re^10: Inclusion of Raku on PerlMonksby 1nickt (Canon) |
on Oct 18, 2019 at 11:54 UTC ( [id://11107655]=note: print w/replies, xml ) | Need Help?? |
I was there too, and I think it's only part of the story. There always has been a small sector among developers/architects/sysadmins who have always known that Perl is vastly superior eg to PHP, and to most languages if your objective is to get a stable working product out the door in the digital era. Perl never went away and has been in continuous use at all the companies mentioned, forms the back end to my text editor, my DB CLI tool, etc etc. I work at one of the largest internet service providers and Perl has never stopped being at the core of the company, and I am not just referring to the cPanel that we provide to tens of millions of customers around the world. I mean many of our internal APIs, DB layers, etc. Sure Perl lost some cachet and lots of market share, and there is quite clearly a huge majority of Pointy-Haired Boss -types who parrot out the conventional wisdom that Perl is out of date and ineffective. But that's not reality. Perl has advanced steadily since taking like 8 years to throw out 95% of the stuff that was ill-advisedly stuffed into it during the era when "Perl6" was thought of as a successor to Perl, i.e. around v5.10 to around v5.18. I believe my friend Your Mother is overstating both the effects of the opprobrobium Perl faces in the real business world, and the benefits of the "contributions" of Liz M and the "Perl6" crew. As someone (chromatic?) said somewhere, "say() and ... ?" Also it irritates me when there are lots of discussions about what is missing from Perl as if that was an established fact. Some of the folks who keep discussing what's needed in core Perl before e.g. a new version number should be used, should get out into CPAN and the real world and see that there's no blocker whatsoever to building today's software with Perl. There is a first-class OOP system in Moo. There is a first-class signatures/type validation/param checking layer in Method::Signatures (sorry that experimental core stuff is Weak!). There is a first-class concurrency layer in MCE. Etcetera. It is annoying to hear non-Perl people repeating myths about Perl's so-called deficiencies, but even more so when it's Perl people who are saying that because they are so focussed on P5P or whatever that they have not kept up with the state of the arts. Do you think SRI and Jan-Henning and Doug Bell and Joel Berger and the rest of the Mojo crew feel at all constrained by Perl's "missing features"? I know we don't at $work. We build better, more reliable, equally scaleable software in far less time than the teams that are building clients against our APIs in Java or .NET or any other framework. Perl rules, and it's counterproductive in my view to keep restating the ancient history of the rise of PHP as if it's the current state of things. Perl has recovered from those days and the misguided steps to stuff every notion of new techniques generated by the "Perl6" crew into it. It still suffers from the effects of the missteps, but it's in widespread and growing use in the corporate world in many sectors. We are a smaller fish than we used to be but the pond is a million times bigger. Bah! When it comes to Perl, the future's so bright I gotta wear shades! update: s/top-shelf/first-class/, thx hippo
The way forward always starts with a minimal test.
In Section
Perl Monks Discussion
|
|