There is a problem with static variables and functions in how it is used by apps and frameworks in PHP , they are used as global functions or parameters while this is by far what they mean. It is easy to write the same functional or even procedural code in PHP using static variables dressed up as OOP. I have nothing against functional programming or even procedural (my work for some years was turning Cobol into Java , and I have seen real diamonds in the way they done it (along of course of rubbish) ) . There is no reason to pretend OOP and use static methods or variables , just use the old way functional or procedural programming , it is clearer.
What static means is that is goes along with the class itself not the instances of that class. In that sense static properties are application scope caching. While most OOP languages have static initializers you can achieve the same thing in PHP with spl autoload. Of course there is no reason to have Form or Input or anything from a specific request as static. This is just functional code in OOP static properties and methods dressed up.
The main problem in PHP is that we don't speak the same language. PHP is multiparadigm , in fact most write PHP apps in many paradigms in the same context. Everyone have its own mix , and I can't find employees understanding what OOP is in PHP. We are not talking the same language. Their impressions came out of something that is a mix , and they haven't tested their opinions. “Everyone in PHP community is saying the X argument” . Have you tested it ?