I wouldn't say its "missing" named function arguments. Treating arguments and return values as lists is very powerful. Perl is very Lisp-like in that aspect. Also, CPAN is considered one of Perl's strengths. How did…
You saying nobody starting web dev should use CGI.pm? Or CGI in general? Because CGI itself has its uses even today. It's much easier to understand and get off the ground than something like Mojo or Plack (I've used…
I consider myself a serious Perl developer, working in a Perl shop for the past 15 years. We still prefer using bless and continue to use it in the present day. It so much lighter weight than the M* systems and I prefer…
The only thing about the JSON package though, when things go wrong, it is very unhelpful about where it goes wrong. I usually end up always wrapping the json_decode in an eval to catch the error and handle it in an…
Even easier than that: my $house = shift; my $color = shift // GetDefaultHouseColor();
I wouldn't say its "missing" named function arguments. Treating arguments and return values as lists is very powerful. Perl is very Lisp-like in that aspect. Also, CPAN is considered one of Perl's strengths. How did…
You saying nobody starting web dev should use CGI.pm? Or CGI in general? Because CGI itself has its uses even today. It's much easier to understand and get off the ground than something like Mojo or Plack (I've used…
I consider myself a serious Perl developer, working in a Perl shop for the past 15 years. We still prefer using bless and continue to use it in the present day. It so much lighter weight than the M* systems and I prefer…
The only thing about the JSON package though, when things go wrong, it is very unhelpful about where it goes wrong. I usually end up always wrapping the json_decode in an eval to catch the error and handle it in an…
Even easier than that: my $house = shift; my $color = shift // GetDefaultHouseColor();