Finally decided that symfony Security component is way too complicated for my little #taproot, so ditching it — but I’ve learnt a lot from digging through it and my further efforts will try to provide some of the amazing flexibility it gives whilst being more performant and easier to understand #php #dev #meta
I’m trying to grow up but it’s hard past a certain age
Ha, love it Aral Balkan :)
aral hideous. That makes me more embarrassed to be a PHP dev than all the bad rep it has as a language. And they're teaching SVN! It gets worse :(
I love that #php now has shiny namespacing and a thriving code sharing community, but I think the heavily hierarchical namespacing practises used by some of the community (e.g. symfony components) are unhealthy.
They are difficult to memorise, relying on (often slow) IDE autocomplete, and encourage a
use statement for each class. That’s pretty much a scoped equivalent of
from x import * in python — not a good practise! It’s still namespace pollution, it just takes longer to write.
I am trying to use a more python–like, package-centred approach with much fewer subnamespaces. The outcome of this should be that you
use the package name:
…and then using all the classes/subnamespaces from that root, e.g:
$t = Posse\Helpers::convertHtmlToTwitterFormat($s);
Doing a mass find-and-replace operation on the Perch Blog app so I can have more than one running at the same time. If you want to do something similar, here are the strings you need to replace:
And then obviously rename the
.class.php files and activate as you would any other app.
Researching #wordpress plugin API as prior art for my activitystreams events framework. Yuk. Yuk yuk yuk.