Perl 7 is going to be Perl 5.32, mostly
I&#x27;ve been a perl zealot since 2005. I didn&#x27;t even know &quot;python&quot; existed until around 2008 when I found a script file with a &quot;.py&quot; file ending in a fresh ubuntu install. I started going to perl conferences sometime after 2010 when someone on irc informed be about them. I learned so much in those conferences, mainly about the alternatives to cgi and the modern OOP &quot;framework&quot; named &quot;moose&quot;. I thought I was in heaven.<p>I landed my first devops position around the 2010 era as well and being the only one on the team that really knew how to &quot;program&quot;, I spammed out tons of perl scripts and web apps. A few years later one of the newer employees on the customer support team started spouting off about &quot;python&quot; and how it was so easy to learn. He was always blabbing about terms I&#x27;d never heard of like &quot;generators&quot;, &quot;list comprehensions&quot;, &quot;decorators&quot;, etc. I looked them up and learned they were just abstract constructs with fancy names that are supported in most any language. So I just figured he was some idiot that didn&#x27;t really know anything. Otherwise, why would you be blabbing about abstract constructs? He quickly landed a job at google and I left and started freelancing only picking up perl jobs. Because perl was &quot;dying&quot; and this being after 2012, there were several companies with large perl bases that couldn&#x27;t find local employees so were forced to allow remote workers.<p>This is where stuff started going wrong. I went through many jobs&#x2F;gigs my first couple of years. I quickly noticed that companies that had large perl code bases were all founded pre-2005. This meant it was crap perl, in most cases not even using CPAN but having home grown ORM&#x27;s and web frameworks and a scrict hate of javascript. So it mostly sucked and was slow going. In one case I was literally fired after a couple of months from this one company that specialized in phone billing accounting software (all perl powered) because I was &quot;too slow&quot;. The owner told me he should have never hired someone with less than fifteen years experience with perl and bid me farewell. I almost busted out laughing as for the entire two months I was only doing javascript front end work since the other perl guys there hate javascript. Even the owner of the company had no clue how his own software worked. This was a theme that repeated it self else where as well.<p>Fast forward a few more years and I had landed a good remote job, still in perl but offered more freedom in the dev cycle. I got good with react and vue.js as it greatly speed up the dev time for all the heavy interactive apps I was tasked with. But I continued to struggle against others in the perl community. I can understand how a 50 year old perl dev (the typical age) would hate javascript and instead put as much code in the back end using all kinds of horrid html templates and never ending form post&#x2F;refresh&#x2F;repopulate cycles... I can see the &quot;why should I learn javascript if i know perl&quot; ideology, but what blew me away is a constant &quot;why should I learn SQL if I know perl&quot; ideology. Yes I&#x27;m serious. In so many other cases devs were fine with just doing &quot;select *&quot; on tons of tables and stuffing all that in a hash&#x2F;dictionary of column name matching keys. Databases were big, scripts and page load times would grow to minutes or even hours. Sometimes exhausting the machine&#x27;s ram and crashing everything. Everyone was fine with it, management just acted like it&#x27;s how things work. Meanwhile as a co-worker, I&#x27;m left digging through pages of perl code that could have just been a single SQL query trying to figure out why some numbers are wrong in an invoice report. It was a continual issue.<p>Another issue is just the bit rot of cpan. The ORM and drivers for both postgresql and sqlite don&#x27;t even support most of the features added in those systems since 2014. So even though postgresql is the most advanced DB out there, you are stuck with no ability to use any of the fancy native array or json types or even the &quot;natural&quot; join syntax (and many other things), neither good support for foreign keys in sqlite either.<p>I&#x27;ve thrown my hands up and jumped ship. It&#x27;s sad too. I liked many in the community and like Larry Wall as well and have had dinner with him on several occasions. But I can&#x27;t keep my sanity and stay with perl. I can read perl fine, it is not the notorious &quot;write only&quot; language that many troll it to be. But the issue is the community and those using perl daily are fine with being stuck in 1995. Larry Wall stopped adding features to perl in 2002 (?) and moved to perl 6 which.... well how do you even describe that? The point is, perl has been the same since 2002, mean while python has had continual development and features added every year since then. I&#x27;m just done.