On Reddit.com there's a post from krakjoe talking about using multithreating in PHP, specifically with pthreads. Unfortunately, there's several misconceptions about the pthreads (and concurrency) that still makes it difficult in PHP. The post lists a few of them:

• PHP is not thread safe, there are lots of extensions that will give your application cooties.
• pthreads is old fashioned
• pthreads does not include everything you need to execute safely
• pthreads unsafely shares memory among contexts in order to provide concurrent functionality
• pthreads is beta and should be avoided at all costs

The author points out that pthreads are still in more of a "beta" state and probably shouldn't be used in production (though some do):

Multi-threading in PHP sounds like some sort of voodoo, for so long it's been something that was either impossible in the minds of php programmers, or a bad idea to try and emulate. pthreads doesn't emulate anything, it leverages bundled functionality and the object API to provide true userland multi-threading.

In his latest post, Wez Furlong responds to some of Jacob Santos' comments made earlier today about Service Data Objects (SDO).

I was just skimming over Santos' Post about SDO, and was saddened to see more anecdotes and less facts.

Specifically, he mentions two points - one dealing with the definition Jacob gave for the functionality and the other pointing out some better stats that Jscob didn't include in his comments.

In his latest post, Wez Furlong responds to some of Jacob Santos' comments made earlier today about Service Data Objects (SDO).

I was just skimming over Santos' Post about SDO, and was saddened to see more anecdotes and less facts.

Specifically, he mentions two points - one dealing with the definition Jacob gave for the functionality and the other pointing out some better stats that Jscob didn't include in his comments.

On php|architect's A/R/T article repository today, there's a new guide written by Sebastian Bergmann - an introduction to PHPUnit.

In the last decade, PHP has developed from a niche language for adding dynamic functionality to small websites to a powerful tool making strong inroads into large-scale, business-critical Web systems. Financial institutions such as banks and insurance companies use PHP, for instance, to develop and maintain solutions for Basel II Credit Rating. Critical business logic like this needs to work correctly. But how do you ensure that it does? You test it, of course.

The tutorial takes a look at how to get started writing tests for your code and how to run those tests against your code to find problems. Sebastian also includes a few of the common misconceptions about unit testing, specifically using PHPUnit to test their apps.

On php|architect's A/R/T article repository today, there's a new guide written by Sebastian Bergmann - an introduction to PHPUnit.

In the last decade, PHP has developed from a niche language for adding dynamic functionality to small websites to a powerful tool making strong inroads into large-scale, business-critical Web systems. Financial institutions such as banks and insurance companies use PHP, for instance, to develop and maintain solutions for Basel II Credit Rating. Critical business logic like this needs to work correctly. But how do you ensure that it does? You test it, of course.

The tutorial takes a look at how to get started writing tests for your code and how to run those tests against your code to find problems. Sebastian also includes a few of the common misconceptions about unit testing, specifically using PHPUnit to test their apps.

In his latest blog post, Andi Gutmans responds to a CNet article and some of the misconceptions surrounding it.

As I mentioned in my response to Edin's blog entry, in the interview I never called out PHP 6 as a Zend product. I *did* talk about what's coming down the pipeline for PHP and mentioned that both Zend and Yahoo! have been contributing to the Unicode effort (which is true).

It's also important to understand that it is *not* in Zend's interest to claim that we are the only company behind PHP, that would make PHP look much smaller than it is which would be very counter productive to our quest for increasing PHP proliferation.

He notes that the only connotation he was implying was that Zend waqs doing its part to help PHP, as a language, to grow and thrive - not that it was the biggest/best/most important at doing so. There are some sensitive topics that the CNet article inadvertently touches on that have caused some problems already, but Andi hopes that his statements here and in the comments on Edin's blog help resolve at least some of the issues out there.

In his latest blog post, Andi Gutmans responds to a CNet article and some of the misconceptions surrounding it.

As I mentioned in my response to Edin's blog entry, in the interview I never called out PHP 6 as a Zend product. I *did* talk about what's coming down the pipeline for PHP and mentioned that both Zend and Yahoo! have been contributing to the Unicode effort (which is true).

It's also important to understand that it is *not* in Zend's interest to claim that we are the only company behind PHP, that would make PHP look much smaller than it is which would be very counter productive to our quest for increasing PHP proliferation.

He notes that the only connotation he was implying was that Zend waqs doing its part to help PHP, as a language, to grow and thrive - not that it was the biggest/best/most important at doing so. There are some sensitive topics that the CNet article inadvertently touches on that have caused some problems already, but Andi hopes that his statements here and in the comments on Edin's blog help resolve at least some of the issues out there.