Comments on: Worker classes in Symfony http://symfonynerds.com/blog/?p=335 Nerds who love the symfony-project Wed, 08 Sep 2010 03:37:44 +0000 http://wordpress.org/?v=2.6 By: Lawrence http://symfonynerds.com/blog/?p=335#comment-746 Lawrence Sun, 27 Dec 2009 04:28:34 +0000 http://symfonynerds.com/blog/?p=335#comment-746 Javi, I see what you mean about the ORM as an implementation detail, on the same level as committing to the framework. But what do you mean by "hiper-language-meta-framework"? I have thought about switching to Groovy/Grails for some of my future work. I worry about how slow PHP is, and how slow Symfony is in particular. On the flip side, I know the core Symfony team is looking to speed the framework up, and Groovy/Grails leads to slightly more sysadmin work, as one ends up having to deal with Tomcat on the server. I don't think I'd ever switch to Ruby/Rails. Once upon a time I was tempted, but nowadays I think Symfony gives the world of PHP most of what one could get from Rails. If I decide to switch to a more expressive language (that supports closures in a graceful manner, and which supports meta programming) then I'd switch to the JVM world. Javi, I see what you mean about the ORM as an implementation detail, on the same level as committing to the framework. But what do you mean by “hiper-language-meta-framework”?

I have thought about switching to Groovy/Grails for some of my future work. I worry about how slow PHP is, and how slow Symfony is in particular. On the flip side, I know the core Symfony team is looking to speed the framework up, and Groovy/Grails leads to slightly more sysadmin work, as one ends up having to deal with Tomcat on the server.

I don’t think I’d ever switch to Ruby/Rails. Once upon a time I was tempted, but nowadays I think Symfony gives the world of PHP most of what one could get from Rails. If I decide to switch to a more expressive language (that supports closures in a graceful manner, and which supports meta programming) then I’d switch to the JVM world.

]]> By: Javi http://symfonynerds.com/blog/?p=335#comment-739 Javi Wed, 23 Dec 2009 13:44:24 +0000 http://symfonynerds.com/blog/?p=335#comment-739 I had the same thoughts as you and I find that using workers is a good idea but I don't really understand the need to add another layer on top of the ORM. IMHO using an ORM is an implementation decission, just like using Symfony instead of Zend or PHP instead of .NET. Why don't use a hiper-language-meta-framework just in case you decide to change to Ruby on Rails one day? :-) BTW, excelent article! I had the same thoughts as you and I find that using workers is a good idea but I don’t really understand the need to add another layer on top of the ORM. IMHO using an ORM is an implementation decission, just like using Symfony instead of Zend or PHP instead of .NET.

Why don’t use a hiper-language-meta-framework just in case you decide to change to Ruby on Rails one day? :-)

BTW, excelent article!

]]> By: Closer To The Ideal » Blog Archive » A new post up at Symfony Nerds http://symfonynerds.com/blog/?p=335#comment-737 Closer To The Ideal » Blog Archive » A new post up at Symfony Nerds Tue, 22 Dec 2009 22:03:54 +0000 http://symfonynerds.com/blog/?p=335#comment-737 [...] I’ve a new post up at Symfony Nerds. This looks at the evil of utility classes full of static methods, a vice that I’m guilty of on every project. I examine possible ways to refactor the code to get a healthier overall architecture. [...] [...] I’ve a new post up at Symfony Nerds. This looks at the evil of utility classes full of static methods, a vice that I’m guilty of on every project. I examine possible ways to refactor the code to get a healthier overall architecture. [...]

]]>