I find this this kind of prejudice towards technologies rather reductionist and limiting, to say the least. During interviews I conduct, broad generalizations t

I find this this kind of prejudice towards technologies rather reductionist and limiting, to say the least. During interviews I conduct, broad generalizations towards any technology, be it Visual Basic or Rust, for example, are noted as red flags. My rationale is that engineers should be able to understand that tooling is a matter of context + tradeoffs. There are lessons to be learned in almost any technology. Even more so in battle-tested technologies. And PHP is still a very popular tool that has come a long way over almost three decades since its creation (mid 1994). Things that come to mind that are worth looking for inspiration in PHP: - package management (composer is great) - gradual typing (9 years of use-cases to learn from) - framework popularity (what makes Laravel so popular?) - staying power (why is it still so popular after 3 decades?) - governance and community development model (continuous improvements since inception and relatively little drama) - backwards compatibility (major changes of internals with very little compatibility breaks. PHP's engine had major core changes while still maintaining friendly levels of backwards compatibility. And JIT is on the way.) https://www.php.net/manual/en/history.php.php https://www.php.net/manual/en/history.php.php