On 24 Mar 2010, at 10:48, Tommy Pham wrote: > On Wed, Mar 24, 2010 at 3:39 AM, Stuart Dallas <stut...@gmail.com> wrote: >> >> On 24 Mar 2010, at 10:34, Rene Veerman wrote: >> >>> On Wed, Mar 24, 2010 at 12:28 PM, Tommy Pham <tommy...@gmail.com> wrote: >>>> >>>> Funny you should mention all that. Let's say that you're longer with >>>> that company, either by direct employment or contract consultant. >>>> You've implemented C because you need 'thread'. Now your replacement >>>> comes in and has no clue about C even though your replacement is a PHP >>>> guru. How much headache is maintenance gonna be? Scalability? >>>> Portability? wow.... >>>> >>> Thanks for posting this before i had to. >>> >>> +1, +1, +1... >> >> You realise, of course, that the same argument applies to using advanced >> features of PHP, such as threading should it ever be supported. >> >> -Stuart >> > > Thanks for supporting PHP thread. Thus, it would be a lot easier for > any PHP guru to scale, make it portable, or integrate into other PHP > apps without having to juggle C, Ruby, Python... and whatever else is > out there...
I don't believe I did support PHP threading. My point was that using advanced features like threading will limit your employee choices in exactly the same way as having a multi-language environment. -Stuart -- http://stut.net/ -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
