Re:Modern PHP without a framework
by megous on Saturday March 31, 2018 @09:25PM
(#16726171)
Is it really less verbose for OOP programming than Java, if you're using type annotations, etc.?
[ Parent
| on HN ]
Java is still burdened with a lot of this.that.this.that.whatever(something)
I don't know that I've ever encountered something like:
RequestProcessorFactoryFactory.RequestProcessorFactory.getRequestProcessor(XmlRpcRequest)
In any other language. And that's not the most egregious example. It's quite common.Have a look at Zend's SDK. It's full of such nonsense. Symfony also tries very hard to look like Java, complete with verbose naming and files paths.
Maybe. I avoid stuff like that. See https://www.slimframework.com
for example.
Re:Modern PHP without a framework
by davidjnelson on Sunday April 01, 2018 @07:44PM
(#16731207)
Seems more like a dig on inheritance and the resultant code than java as a language.
Well, two layers of factory classes, one calling the other, plus a big xml blob is pretty Java specific. I'm open to to common counter examples in some other language.
There's inheritance, and there's overindulgence.
Re:Modern PHP without a framework
by davidjnelson on Saturday April 07, 2018 @01:57PM
(#16781826)
Interface based polymorphism is pretty useful. Been thinking more functionally lately, and can’t remember needing it. Parametric polymorphism ( aka generics ) are still useful for the immutable state graph.