Hi internals, I’m a developer who uses both Java and PHP regularly, and I’m writing because I care deeply about PHP’s future.
I’ve been following the language’s evolution closely, especially since PHP 7 and PHP 8. I’ve noticed a growing trend of adding features that feel very "enterprise-oriented" — such as typed properties, attributes, and property hooks. While I understand the value of these features in certain contexts, I can’t help but wonder: is PHP intentionally following Java’s path? I ask this not as criticism, but out of genuine curiosity about the language’s direction. PHP’s traditional strength has been simplicity, pragmatism, and being web-native. Java, on the other hand, excels in large-scale enterprise ecosystems with strong type safety and tooling. >From a developer’s perspective, when I see PHP adding more Java-like features, it makes me question whether the goal is to compete with Java in the enterprise space — or if these additions are meant to solve specific problems without changing PHP’s core identity. I’d really appreciate it if you could share some insight into how the internals team views this balance. Is there a conscious effort to avoid making PHP feel like "Java for the web"? Or is the thinking that these features are simply useful tools, regardless of where they originate? Thank you for all the hard work you put into maintaining and evolving PHP. I’m looking forward to understanding more about where the language is headed. Best regards, [haoqin]
