ramblings on PHP, SQL, the web, politics, ultimate frisbee and what else is on in my life
Symfony2 community pushing the PHP ecosystem
Even if you don't care about Symfony2 or Silex and instead prefer some other framework, there is stuff to benefit from going on inside the Symfony2 community. Not only are the Symfony2 components all build to also work standalone, but key contributors are also building libraries and tools that should proof useful for the entire PHP ecosystem. For an overview of the components part of Symfony2 I refer you all the Symfony2 site. Here is a short overview in alphabetical order of libraries that have spawned around Symfony2 (and just to clarify not at all focused on just Symfony2). Common to all of them are that they require PHP 5.3 and follow the PSR-0 for class loading.
Symfony CMF: why, how, when (summary)
In my love affair to always be a bit verbose it seems like some key points (no Java requirement in the final version for example) were made clear enough. So here is a short summary:
Symfony CMF: why, how, when (part III)
And now for the final post in this series, unless I start to get some serious questions :)
Symfony CMF: why, how, when (part II)
Continuing with my post from the other day I will try to answer some of the questions that seem a bit reoccurring.
Symfony CMF: why, how, when (part I)
I have blogged about how I wish there was a developer friendly CMS for a while now. I have also blogged that I wish that top applications would be build on top frameworks instead of homegrown ones. I have also blogged how I hope for the Symfony CMF initiative for solve all of this. Now back in fall 2010, when the community agreed to pursue using the Java Content Repository (JCR) specification as the basis for our work, things kinda fell in to a hole. The vision seemed clear and one of the main benefits was that we could get going faster. At the same time the number of Symfony2 developers were few and they were mostly busy keeping their projects in sync with the on going development. So in the end it was basically Liip that kept pushing things forward by continuing to invest into Jackalope (the connector between PHP and Java implementation of the JCR spec) as well as a Doctrine2 ODM implementation on top of this. One area where there was in fact a fair bit of community feedback was in how to better PHP-ify the JCR specification which was more or less literally translated to PHP in the original PHPCR implementation.