2012: A Year in PHP

Re:2012: A Year in PHP by tiwazz on Tuesday January 08, 2013 @03:51PM (#5028432)

Am I the only one that finds these deeply nested namespaces completely unusable?

https://github.com/symfony/symfony/blob/master/src/Symfony/B...

I thought the point of autoloading was to make things easier, not to replace require_once with something more verbose. Why should I have to import classes from within my own package?

[ Parent | on HN ]

Re:2012: A Year in PHP by contingencies on Tuesday January 08, 2013 @07:10PM (#5029328)

You're not alone.

It's a symptom of people trying to solve everything with one toolset ("Me know hammer, me use hammer!").

In practice, most OO projects regardless of language have classes like 'LatestThingOtherThingIKindaRememberSomethingSomeoneElseWroteDontTouchIt', combined with a non-negotiable and often intrinsically (looking directly at any given piece of code) inexplicit set of dependency assumptions around the global object model.

In general we need less OO, and more immediately apparent, procedural, loosely coupled code. Programs that "do one thing and do it well".

[ Parent | on HN ]

Re:2012: A Year in PHP by stephenr on Thursday January 10, 2013 @03:57AM (#5036097)

Just because symfony has fucked naming and use of namespaces doesn't mean namespaces are bad.

[ Parent | on HN ]

Re:2012: A Year in PHP by nachteilig on Tuesday January 08, 2013 @04:40PM (#5028685)

I don't find it _completely_ unusable, but I'll admit that it's pretty frustrating.

[ Parent | on HN ]