> A majority of the web still runs on some variant of PHP, and that guarantees that it's not dying anytime soon.
The same is true of Perl, but (depending on your definition of "not dying") it's not clear that Perl isn't dying.
The same is true of Perl, but (depending on your definition of "not dying") it's not clear that Perl isn't dying.
When you've been doing this a while, you can appreciate what e.g. Python gives you in structure, maintainability, and lack of foot-guns.
But when you're still in the "how does this work? Why won't this work? It worked!" phase, having less boilerplate, and fewer non-problem domain concerns (types? modules? tuples? Say what you mean, Old Man!) might be really valuable.
I think the best thing I remember about PHP is probably its online manual. Each library function had a few full use cases underneath.
However, modern php isnt being sold as index.php and a mysql connection. It's Doctrine, composer and laravel/symphony. Which have their fair share of boilerplate.
>I think the best thing I remember about PHP is probably its online manual. Each library function had a few full use cases underneath
The problem with PHP is that you need the online manual everytime you want to use a function because the argument order is so inconsistent.