I assume everyone reading this site is a software engineer of some flavour. If you aren't this site must be incredibly dull. As such, there is no need to include basic introduction like “what is MVC” 1. I am reading up on symfony2.
Due to my “comprehension first” personal requirement, straight tutorials are less valuable than “architecture notes”. Trained in how-to-do something (as example Q&A 2) is less valuable than knowing hows its built, so you can use and abuse it properly. My goal is design patterns 3, not a page of screen shots.
* THis is an index
Bundles are an important thing to Symfony. If you have a small project, this isn't an issue. For larger longer-lived SOLID projects you may wish to be able to change frameworks 4 5. With good code structuring this is achievable.
The important decisions in Symfony seem to be made in config files 6 7. I was using the YML variant, although there are other formats available. I like this method over some of the other OO frameworks, as its more concise. Relationships between entities and string param are flat lists of data, and don't really fit into the idea 'Object'. You can't pass messages to a flat list (or alternatively, the message response is all of the flat list).
Before I started using composer 8, I suspected it would cause problems. It is alot better technology than the two generation previous (rpm, dpkg), but there is complications. I am using bleeding-age code, where people are adding things like ./test; so it doesn't rollout automatically. I think I ought to use the dryrun mode more, but that is not a failure of the technology.
To say what Symfony is ~ precisely ~ is abit confusing. Symfony is a product. Symfony isn't so much a singular software library. Quite a large amount of Symfony is composed from other libraries, that have been published separately 9 10 * 11 12. This is good engineering practice, and allows more rapid development. This is an entirely different perspective to big corporate platforms (e.g. Oracle platform, which includes its own Linux distribution, and web-development tools). If I wish to scale Iceline to the same enterprise level, I would probably do exactly the same thing (although importing the important bits of Iceline into a bundle that can be run inside Zend or Symfony is probably a better solution).
I want to make this one of the tools I use, not become a Symfony developer. When its repetitive, it should be automated. I want to keep generic application frameworks, such as gearman available. I wrote this before my last course on architectures, and the lecturer said ~ in the course ~ everything that I just wrote. The generic reading on Symfony was duplicate material or poorly structured for software engineers (this is another MVC framework). What I was reading wasn't architecture notes, although that was my search term.
* This was uploaded to github by Fabien Potencier who is the architect for Symfony.