3 ms·
Dynamic types, and less verbose. Which, I agree, can be downsides as well.
by tyingq 9y ago
Dynamic types, and less verbose.
Which, I agree, can be downsides as well.
- megous 9y agoIs it really less verbose for OOP programming than Java, if you're using type annotations, etc.?
- tyingq 9y agoJava 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.
- cutler 9y agoHave 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.
- tyingq 9y agoMaybe. I avoid stuff like that. See https://www.slimframework.com https://www.slimframework.com for example.
- davidjnelson 9y agoSeems more like a dig on inheritance and the resultant code than java as a language.
- tyingq 9y agoWell, 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.
- davidjnelson 9y agoInterface 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.