What SUCKS Most about Learning Perl Programming in 2020 !

► Free 7 Step Freelance Perl Developer Guide:

Freelance Guide


► 6 Figure Freelance Web Developer Kickstarter – $19.99

6 Figure Freelance Web Developer Kickstarter

► 30 Day SQL Project Launchpad – $49 for 2 months or $77

30 Day SQL Project Launchpad

► 30 Day Python Project Launchpad – $60 for 2 months or $97

30 Day Python Project Launchpad

► Cracking the Programming Interview Guide – $100 for 2 months or $179

Cracking the Programming Interview Guide


► Personal Video Consultation Request – $49.99

Career Consultation


► Facebook Group: https://www.facebook.com/groups/rodtheitguy/
► Instagram: https://www.instagram.com/rodtheitguy/
► Twitter: https://twitter.com/rodtheitguy
► Facebook Page: https://www.facebook.com/rodtheitguy/
► Email: https://digilinksolutions.net/contact/

► Join DigiLink Tech Community:


► Discord Community:

This video gives you insight about What SUCKS Most about Learning Perl Programming in 2020 !

Related Topics:

perl programming, perl , perl tutorial, make money programming , how to make money coding ,how to make money as a programmer, developer jobs , developer interview , coding interview,software developer resume , programming interview , day in the life of a software engineer , coding projects , web development projects , software developer career , web developer portfolio , how to get a programming job , software engineering career , self taught developer , self-taught programmer , Stefan Mischook , Andy Sterkowitz , Rod the IT Guy

22 thoughts on “What SUCKS Most about Learning Perl Programming in 2020 !

  1. Ofcourse, I agree with this guy. Ofcourse if you are an experienced Perl guy (basic, intermediate, advanced), you must do Python. Because then you'll realise how truly fabulous Perl is!! And how it simply blows Python out of water when it comes to regex (use the qr function toake regex even more flexible and powerful ) , or how Perl's map and grep are far more powerful than list comprehensions, or how much control you can gain from "my" and "our" variable scoping.
    Or, just read the replies to a comment where a software engineer used Perl to gather data from CSV files that were 50GB± in size.
    Python dictionary crawls at such requirements.

  2. Honestly – the programming language and/or syntax is just the half of it – the real key in any environment is to actually learn/know about the business logic the program needs to serve. That should always be the focus.

    I find youtube full of videos "about" programming languages but the fact is that it should not be about the programming languages rather it should be about the algorithms but seldom we find that.

    More of less we always end up witnessing a comparison between 2 languages – which could be useful in certain situations – but is not paramount.

  3. Perl is great for text processing and other tasks like that and its pretty much cross-platform, but I think macos is going to start shipping without it rip

  4. activestate in regards of "corporate backing". we have a lot of legacy perl stuff on UNIX and the major problem I have with perl is the readability, you can do stuff in thousand different ways and sometimes it's super hard to wrap your head around what the initial programmer was thinking and that's the major point for us using python nowadays.

  5. The nice and shiny language of today produces the legacy code of tomorrow. If a language had huge success at some point (like perl) there is probably a lot of legacy code to maintain (maybe not even classic "legacy code" but long running projects where its just not suitable to restart from scratch).
    Would I advise someone to learn Perl when they just start? No probably not. Pick it up as another language under your belt? Sure. Are there jobs for Perl Programmers? definitely.

  6. I'm a Perl developer, as in specialized in Perl. To this day:
    1) I rarely need to look for projects. I get directly contacted by recruiters that are desperate because they need a senior Perl developer and can't find it.
    2) I generaly can ask for much higher salaries than I can find on other languages, and even get to push up the initial offer limit.
    3) I don't have competition in most cases. I'm pretty used to get interviewed and sent an offer almost immediatly.
    4) I get greatly surprised to see that more and more companies are using modern Perl these days, so dealing with legacy code is becoming rare.
    Is it the best bet to find a job these days? Probably not. Is it worth it getting specialized in Perl? Hell, yes.

  7. Perl has many niche groups: Bioinformatics is huge with Perl. Perl is big in devops. Finance is huge with Perl. One of the best keep secrets is that most major finance players on Wall Street today have rooms full of Perl devs crunching numbers and managing massive databases in Perl at lightning speeds. I call it the "best kept secret" because intellectual property is so tight in that market that anybody working there isn't allowed to talk about it. Perl also happens to be the language with the absolute best support for Unicode out there today hands down. If you want to write code that's going to be useful to people in a global market, choose Perl. There isn't a fortune 500 company without Perl devs.

    Jobs are all about supply and demand. Want to be an interchangeable cog in the machine making $50k per year, pick a language like Python, Java, or whatever the buzzword of the week happens to be. Want to be an indispensable part of a company with your own office making $150k per year, pick a language like Cobol or Perl. It may not be a "cool" language, but that's exactly why it has the highest paying jobs. Perl jobs are out there. You just need to know where to look.

    Perl does have some corporate backers, though not at the level of Oracle. Booking.com, cPanel, and Craigslist are all big backers of Perl (all of those written in Perl, by the way).

    Want a newer language? Check out Raku (the Perl offshoot formerly known as "Perl 6"). Or check out the work being done on the new Perl 7 right now. The language may have a long history, but today's Perl is not the same Perl of 20 years ago. The language has a very active community of people actually using it. The "Comprehensive Perl Archive Network" ("CPAN") is the envy of every other language with a massive repository of user-contributed open-source code. And the Perl language itself is actively managed and updated regularly.

    One final point: If you really want to be employable, don't put all your eggs in one basket. Learn as many languages as you can. Employers are not all that interested in one trick ponies. A person that can show that they know many languages shows that they have the ability to learn and adapt quickly and employers really value that.

  8. That thumbnail is totally misleading. I came here expecting to get mad at some Perl bashing, however, your take on the job market aspect was absolutely correct. Good job on the clickbait.

  9. I'm not sure what job market you're talking about, but here in London programmers are abandoning Perl far more quickly than companies can rewrite their systems. Which means that programmers with Perl experience are in demand and can command pretty good salaries.

  10. I don't get the hostility, it may have gone into shadows a bit but it's still a very useful and fun language to use. It's often rejected as dead by people who are chasing the trendiest language. In reality the language is actively developed with new major version coming out very soon, has an active and dedicated community and amazing backwards compatibility model.

    While it's true there are not as many jobs out there anymore, some big names actively use the language, like Duck Duck Go and Booking.com. Some statistics I've seen say that Perl jobs are actually very high paying compared to other languages. Even if you're not being paid for Perl code, it is still one of the greatest automation tools. I'm pretty sure I use it at least once a month in my day job to scrap data, transform files, automate git and stuff like that

  11. I knew that I subscribed for a good reason. This is the core skill that every programmer should have: know what's good, and why it's good, and, as important, know what sucks, and why it sucks, so you can avoid it. There's too many ways to do what you want to do, so you always have to figure out what you're going to use to do it based on documentable pros and cons.

Leave a Reply

Your email address will not be published. Required fields are marked *