[patricklouys]

I like to use the same approach, I even wrote a tutorial [0] and a book [1] about it.

That being said, I am still forced to use Symfony at my current job. It only gets in the way sometimes, it's not too bad.

On my previous job we went from CodeIgniter to frameworkless and I really liked that. Not having framework constraints working against you was really enjoyable to work with.

[0] https://github.com/PatrickLouys/no-framework-tutorial

[1] https://patricklouys.com/professional-php/

[jwdunne]

I recently gave Sylius, based on Symfony, a spin. I wanted to add a field to a product, editable in the admin area. The additional code and the extensions were ok. Some of the config changes are understandable but I thought it a bit much when the number of additions to configuration outstripped the amount of code required.

[patricklouys]

I feel your pain. That's my biggest gripe with Symfony. Sometimes it feels like I am spending more time configuring that programming.

[cutler]

Rewind to 2005. Isn't this why Rails was born?

[jwdunne]

Funnily enough, I chose a Rails e-commerce solution, Solidus. I added the same feature, 0 configuration, similar if not less code required.

Unfortunately I'm the only one who knows Ruby but I have every faith that my colleagues can pick it up.