The problem is that C code has a much higher maintenance cost. You cannot change C code as fast as you can change PHP code. Plus the amount of C/ZendEngine code necessary to port some PHP code is really big. And for shared hosting/non performance critical applications you still always need to ship the PHP code, and then make sure that changes to the PHP code get synchronized to the C code.
Very annoying problems start to pop up. And that is why scripting languages like PHP, Ruby, Python exist in the first place. On Wed, May 9, 2012 at 4:38 AM, omissis <[email protected]> wrote: > Well the Twig C Extension is going more or less in the same direction, > even though in a less hardcore way :) > > I haven't tried it yet but as Rasums pointed out a couple of years ago > during the Drupalcon Copenaghen, there's a lot of room for performance > improvements by bringing some php code to c, especially for the rendering > part(at least that was true for Drupal, but the fact that some functions of > Twig have been ported makes me quite confident it's the same here, too). > > Clearly the more C the better in terms of performances, but I think it > would be a little overwhelming to rewrite Sf2 in C.. Caching is a way > cheaper alternative for making anything faster :) Still, doing some > benchmarks might point out a few bottlenecks that might benefit a lot from > some C code rather than plain old php. > > On Sunday, May 6, 2012 5:42:19 AM UTC+2, kiang wrote: >> >> A friend recommended this framework - Phalcon ( http://phalconphp.com/ ). >> >> I haven't tried to look deeper. But the concept is simple, let the >> framework you are using works as php extension and it should be faster than >> ever. >> >> It will cause some side effects like that there will be less >> plugins/bundles available as people knowing php doesn't mean they know >> c/c++. >> >> It reminds me there's hiphop-php( https://github.com/facebook/** >> hiphop-php <https://github.com/facebook/hiphop-php> ). But hiphop-php is >> not stable for general usage as it's only focus on the needs from facebook >> itself. >> >> Just want to know if there's anything wrong above and looking for some >> ideas around this. ;) >> >> --- >> kiang >> > -- > If you want to report a vulnerability issue on symfony, please send it to > security at symfony-project.com > > You received this message because you are subscribed to the Google > Groups "symfony developers" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/symfony-devs?hl=en > -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en
