I'll start off by saying I don't know shit all about PHP on a fundamental level. What I have noticed is there there is a sweet-spot of developers, engineers tha

I'll start off by saying I don't know shit all about PHP on a fundamental level. What I have noticed is there there is a sweet-spot of developers, engineers that need to be involved. Comments for "Adobe confirms it won't support Android" [1] are typical. Achshar writes[2], "I think the problem isnt flash itself but the fact that it's proprietary. This is the reason we have such news in the first place. If adobe drops support, it's dead. No such thing with open stuff. No one entity has all the control. This is where html5 upper leg, no one can suddenly start charging you for using it or dictate it's development." K, so if being open is what prevents crap, then why are we here talking about PHP? Maybe its that there are too many hands in the cookie jar. Maybe too many people working on fundamental design is the problem. Whether its A/B testing of choices or how many people should work in a group together – numbers matter. And maybe being too open, rather, too many (different) people working on the same spec, can also be bad as well. [1] http://news.ycombinator.com/item?id=4175399 http://news.ycombinator.com/item?id=4175399 [2] http://news.ycombinator.com/item?id=4176485 http://news.ycombinator.com/item?id=4176485